Summary: | sys-libs/pam-0.75-r9 does not compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ebnf |
Component: | [OLD] Library | Assignee: | Donny Davies (RETIRED) <woodchip> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alex, bart, crude, h3y, pfeifer |
Priority: | High | ||
Version: | 1.4_rc1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ebnf
2002-10-24 10:00:17 UTC
did your glibc versions switch around recently? I remember now upgrading my glibc a few days ago so I did an `emerge -p -C glibc` to see what I had installed and it says both 2.3.1 and 2.2.5-r7 are on my system. How can I determine which version is getting used, and/or switch between versions; I assume 2.3 would break API compatability with 2.2. Since I did an `emerge -u world` with the newer version of glibc, shouldn't there only be a single copy? do an (re)emerge on glib-1.2.10-r4.ebuild ie. 'emerge /usr/portage/dev-libs/glib-1.2.10-r4.ebuild' then an (re)emerge on glib-2.0.6-r1.ebuild ie. 'emerge glib' or 'emerge /usr/portage/dev-libs/glib-2.0.6-r1.ebuild' or any other appropriate way you feel like doing this... that should fix your issue with pam. if you updated to glibc 2.3.1 you'll have this problem until you recompile the aforementioned with the new glibc... plus your other static libs will be needed recompiled as well. if you're to stay will 2.3.1 better fix them as well. regards, _j_ I haver this problem and rebuilding glib doesn't help me. Maybe try to recompile all static libs & then see. After upgrading to glibc-2.3.1, I followed Comment #3 (re-emerge both version of glib). Pam emerged fine after that. OK, I had only compiled glib 2, not glib 1. Doing that fixed it for me. yay happy pam people :) |