A number of distributions are now shipping PAM linked against Glib2. I think that the Glib1 dependency in PAM is rather annoying. I have written a patch that will allow it to link against Glib2. I'm still not sure if this breaks anything. If it doesn't, consider inclusion in the main portage tree. I made a PAM overlay and changed the Glib1 dependency to a Glib2 dependency. Then, I made the ebuild apply this patch. Reproducible: Always Steps to Reproduce:
Created attachment 44198 [details, diff] Path for Glib2
I don't mind moving it to work with glib2, but we do link it statically so that if you break glib2, PAM doesn't break and stop you getting into your system.
I see. I just patched one Makefile, the one in pam_console, which isn't even officialy part of PAM. It's a module that Gentoo has added. I'm not entirely sure that it works though. When it was compiling, there were a lot of warnings about things like "Symbols Redefined" and "Unused Variables" and a lot of functions with two underscores before them, like __function. Does that mean anything?
Silly fix as follows seems to work, though I'd hope something better comes out soon. In the glib ebuild added --enable-static to the econf stanza (glib-2.4.8.ebuild). emerge glib Under /usr/lib mv libglib.a save-libglib.a (it was ancient, dating to 2002). ln -sf libglib-2.0.a libglib.a. Hope I didn't break anything critical. -- TWZ
Already done for soon to be added pam-0.78 (which now links default to glib2).
