Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: net-misc/openssh-4.2_p1-r1 issue
Date: Thu, 09 Mar 2006 08:56:48
In Reply to: [gentoo-amd64] net-misc/openssh-4.2_p1-r1 issue by "R. Müller"
R. Müller posted <440FE5C9.1010606@××××××××××××××.de>, excerpted below, 
on Thu, 09 Mar 2006 09:22:33 +0100:

> hi group, > > my update world stopped at > > [ebuild U ] net-misc/openssh-4.2_p1-r1 [4.2_p1] -X509 -chroot -hpn > +ipv6 -kerberos +ldap -libedit +pam (-selinux) -sftplogging -skey > -smartcard -static +tcpd 0 kB > > with following error message on configuration check : [...] > checking for pam_set_item in -lpam... no > configure: error: *** libpam missing > > !!! Please attach the config.log to your bug report: !!! > /var/tmp/portage/openssh-4.2_p1-r1/work/openssh-4.2p1/config.log > > but "libpam" is already installed : > #emerge -s sys-libs/pam > > * sys-libs/pam > Latest version available: 0.78-r3 > Latest version installed: 0.78-r3 > > #find /usr/ -iname "*libpam*" > /usr/lib64/libpam.a > /usr/lib64/ > /usr/lib64/libpamc.a > /usr/lib64/ > /usr/lib64/libpam_misc.a > /usr/lib64/ > > # ldconfig -p | grep libpam > (libc6,x86-64) => /lib/ > (libc6) => /emul/linux/x86/lib/ > (libc6,x86-64) => /lib/ (libc6) => > /emul/linux/x86/lib/ (libc6,x86-64) => > /lib/ (libc6) => > /emul/linux/x86/lib/ > (libc6,x86-64) => /lib/ (libc6) => > /emul/linux/x86/lib/ (libc6,x86-64) => > /lib/ (libc6) => > /emul/linux/x86/lib/ (libc6,x86-64) => > /lib/ (libc6) => /emul/linux/x86/lib/ > > has anybody a hint ?
OK, I don't know why it's in system as I don't need it, and indeed, have it package.provided so portage won't try to install it when I don't want or need it, instead, pretending it's there, with no ill effects I can see. Unless you know you need it (you ssh into or outof your box), you could (and should, given that it's good security practice not to have installed stuff that you aren't using, not to mention the bother upgrading it on a from-source distribution like Gentoo) probably package.provided it as well. If you /do/ actually need it... Often, those errors have to do with it either looking in the wrong place, or finding it, but testing with a little dummy compile that fails or warns for some strange reason. IOW, it's not because you don't have it, but because the test for it fails for whatever reason. Tweak the test so it detects it correctly, and the problem disappears. That's why it mentions config.log, which will be in your PORTAGE_TMPDIR, in the working dir for that package. Look in it, and it'll tell you what line of configure failed and give some more details. If you know bash scripting, you should then be able to look in the configure script around the given line and figure out what it's testing and run that command from the command line if necessary to see what's going wrong and fix it. Meanwhile, it suggests you bug report it (meaning not here, but at Have you done so, and in the process, checked to see if there's already a bug open on that problem, which might have a solution? If not, I'd suggest you do so. Meanwhile, posting here is a good idea to see if anyone else has come across the problem, but that's not the same as filing a bug, or looking to see if anyone else has filed one and seeing what the comments on the bug say might help. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in -- gentoo-amd64@g.o mailing list