Bug 379267 – sys-auth/pam_mount-2.13 needs libcryptsetup.h (sys-fs/cryptsetup?) regardless of USE=crypt

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Dennis Schridde 2011-08-15 13:59:11 UTC]

With USE=-crypt:
ehd.c:30:27: fatal error: libcryptsetup.h: No such file or directory  CC     misc.o

I assume sys-fs/cryptsetup is required to provide that header.

build.log attached.

Reproducible: Always

[Comment 1 Dennis Schridde 2011-08-15 13:59:30 UTC]

Created attachment 283429 [details]
build.log

[Comment 2 Matt Turner 2011-08-16 03:05:12 UTC]

Confirmed. Even with cryptsetup installed, USE=-crypt emerge =pam_mount-2.11 fails with cryptsetup-related linking error. USE=-crypt =pam_mount-2.10 works as expected though, so this is a regression from 2.10->2.11.

[Comment 3 Matt Turner 2011-08-18 00:02:52 UTC]

Fixed. Thanks for the report!

[Comment 4 Dennis Schridde 2011-12-16 15:56:21 UTC]

Back in sys-auth/pam_mount-2.13, reopening.

[Comment 5 Dennis Schridde 2011-12-16 15:57:15 UTC]

Created attachment 296047 [details]
build.log (sys-auth/pam_mount-2.13)

[Comment 6 Marian Kyral 2011-12-17 10:29:02 UTC]

Can confirm.

[Comment 7 Dennis Schridde 2011-12-26 19:08:15 UTC]

Issue persists.

[Comment 8 Dennis Schridde 2011-12-29 23:58:35 UTC]

Created attachment 297357 [details, diff]
patch for pam_mount-2.13, apparently fixing the issue

[Comment 9 Marian Kyral 2012-02-10 09:29:42 UTC]

(In reply to comment #8)
> Created attachment 297357 [details, diff] [details, diff]
> patch for pam_mount-2.13, apparently fixing the issue

Thanks, I'm able to build it now.

[Comment 10 Marian Kyral 2012-02-10 09:52:25 UTC]

Upstream bug report created: https://sourceforge.net/tracker/?func=detail&aid=3486490&group_id=41452&atid=430593

[Comment 11 rafnov 2012-02-16 10:29:45 UTC]

(In reply to comment #9)
> (In reply to comment #8)
> > Created attachment 297357 [details, diff] [details, diff] [details, diff]
> > patch for pam_mount-2.13, apparently fixing the issue
> 
> Thanks, I'm able to build it now.

Doesn't work for me. How did you do that?

[Comment 12 Marian Kyral 2012-02-16 22:35:19 UTC]

(In reply to comment #11)
> (In reply to comment #9)
> > (In reply to comment #8)
> > > Created attachment 297357 [details, diff] [details, diff] [details, diff] [details, diff]
> > > patch for pam_mount-2.13, apparently fixing the issue
> > 
> > Thanks, I'm able to build it now.
> 
> Doesn't work for me. How did you do that?

From pam_mount-2.11.ebuild I've used following lines:

 > inherit eutils multilib autotools

 > src_prepare() {
 >     epatch "${FILESDIR}"/${P}-fix-build-without-cryptsetup.patch
 > 
 >     eautoreconf
 > }

And copied the new patch as pam_mount-2.13-fix-build-without-cryptsetup.patch

[Comment 13 Francisco J. Vazquez 2012-12-24 20:12:01 UTC]

After almost a year it seems like upstream won't fix it. Will 2.13 remain bugged forever in portage? The patch for 2.11 is there. Please apply it for 2.13 too.

[Comment 14 Matt Turner 2012-12-29 04:53:59 UTC]

Fixed in 2.13-r1.