Bug 380307

Summary:	app-admin/sudo-1.8.1_p2 fails with -ldap
Product:	Gentoo Linux	Reporter:	David Flogeras <dflogeras2>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED NEEDINFO
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log from failed compile attempt emerge --info as requested emerge --info from another system

Description David Flogeras 2011-08-23 01:03:54 UTC

I have a machine running the desktop/kde profile, but with -ldap defined in make.conf since I don't use ldap.  sudo-1.8.1_p2 will not compile (error: timestr.lo is not a valid libtool object)

I've tried running lafilefixer --justfixit, to no avail.  It seems this .lo is within the sudo build tree, not a system libtool file.

Build works fine on another machine with the only (seemingly) difference being it does not have -ldap in make.conf

I'll attach the build.log

Reproducible: Always

Comment 1 David Flogeras 2011-08-23 01:04:26 UTC

Created attachment 284287 [details]
build.log from failed compile attempt

Comment 2 David Flogeras 2011-08-23 01:20:25 UTC

Although the only apparent difference I can notice is -ldap, I tried a USE="ldap" emerge -1 sudo, and it pulls in openldap, but still fails.

I'm not sure if it's more complex than that, and I would have to rebuild all apps with USE=ldap (openssh, etc.), but I'll stop guessing for now until a dev has a look at tells me if I'm just seeing ghosts.

Comment 3 David Flogeras 2011-08-29 17:08:56 UTC

Same thing just happened on an x86 machine I manage (now that sudo 1.8 is stable there), with ldap enabled, so maybe the USE flag suggestion was a red herring

app-admin/sudo-1.8.1_p2 [1.7.4_p5] USE="ldap pam -offensive (-selinux) -skey"

Still fails the same way as originally reported.  Some of my machines upgraded fine, 3 of them failed. I have yet to find the common thing they share.

Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev

2011-08-29 17:50:07 UTC

Please provide emerge --info.

Comment 5 David Flogeras 2011-08-29 19:50:47 UTC

Created attachment 285033 [details]
emerge --info as requested

Comment 6 David Flogeras 2011-08-29 19:51:02 UTC

Created attachment 285035 [details]
emerge --info from another system

Comment 7 David Flogeras 2011-08-29 19:51:43 UTC

Hey Diego, I've attached emerge --info from two of the machines that were failing.  However, since then I tried another emerge -1 sudo, and it worked.  Perhaps the recent portage upgrade changed something?

Comment 8 Diego Elio Pettenò (RETIRED) gentoo-dev

2011-08-29 21:10:40 UTC

Rather likely a problem with distcc from the build log.

Comment 9 David Flogeras 2011-08-29 21:50:14 UTC

That never occured to me.

The first machine (emerge.info.one) is an x86 machine, which uses an amd64 machine with i686 cross compiler installed for distcc (followed cross-distcc guide).

The second is amd64, and it's "helper" is also amd64.  Not sure if that helps, but I know of at least one package (chromium) where cross-distcc does not work and I have to temporarily disable it.  However, amd64 host and amd64 distcc peers has never failed on that. In this case (sudo) it was failing to compile on both setups.

If you need anything else, please let me know.