I installed gentoo and did a emerge -u system All packages compiles and installs nicely except for pam-login-3.10. gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I. -I. -I.. -I. -DLOCALEDIR=\"/usr/share/locale\" -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual -Winline -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wshadow -Wstrict-prototypes -Wundef -Werror -O2 -pipe -O2 -pipe -c `test -f 'setproctitle.c' || echo './'`setproctitle.c cc1: warnings being treated as errors In file included from /usr/include/netinet/in.h:212, from /usr/include/netdb.h:28, from login.c:63: /usr/include/bits/socket.h: In function `__cmsg_nxthdr': /usr/include/bits/socket.h:277: warning: cast increases required alignment of target type make[2]: *** [login.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/pam-login-3.10/work/pam_login-3.10/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/pam-login-3.10/work/pam_login-3.10' make: *** [all] Error 2 !!! ERROR: sys-apps/pam-login-3.10 failed. !!! Function src_compile, Line 29, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1.emerge -u pam-login 2. 3. Actual Results: cc1: warnings being treated as errors... <snip> /usr/include/bits/socket.h:277: warning: cast increases required alignment of <snip> !!! ERROR: sys-apps/pam-login-3.10 failed. System is a Sun Ultra 5 with an Ultrasparc IIi CPU.
Strange! It emerges on all my Sparcs without any problem. The includes come from glibc. What glibc/gcc/binutils versions do you have? What version of pam-login is currently installed? Does this version still compile fine right now? (emerge =sys-apps/pam-login-......)
I currently have pam-login-3.7. I re-emerged it and it still compile fine. gcc is 2.95.3 (gcc-2.95.3-r7) glibc 2.2.5 (glibs-2.2.5-r8) binutils is 2.11.92.0.12.3 (binutils-2.11.92.0.12.3-r2) All latests.
Your version are much older than mine. I use the following versions. sys-devel/gcc-3.2.2 sys-devel/binutils-2.13.90.0.18 sys-libs/glibc-2.3.1-r4 Hard to tell what causes the problem. GCC, Glibc or maybe both. Does some developer still have a machine with at least glibc 2.2.5 installed? I guess searching for someone with gcc 2.95.x is already hopeless.
I see!! I'm new to 64 bit architecture. I thought maybe 2.95.3 was still the compiler used. I will not trust emerge -u blindly anymore :^) I will upgrade gcc, glibc and binutils. Thanks for your time and for a quick response!
It sounds like you are running the default-sparc64-1.0 profile, is this so? I can build up a 1.0 system and test if this is the case
If you do a fresh installation, i highly suggest using the 1.4 profile. I would run 1.0 only if it has been installed an running stable for months but not on any fresh installation anymore. Anyway, it's a bug and we need a fix. If pam-login 3.10 fails all the time on a profile 1.0 sparc64 we should consider limiting the version to >= 3.7 in "packages" of default-sparc64-1.0. Hints from other devs?
this looks like the default-sparc-1.0 profile, therefore from the package list for that profile these are the base values for glibc/gcc/binutils *>=sys-devel/binutils-2.13.90.0.14 *=sys-devel/gcc-2.95.3-r7 *>=sys-libs/glibc-3.2.1-r2 meaning, gcc is (correctly) locked at 2.95.3-r7 binutils must be 2.13.90.0.14 or higher, and glibc must be 3.2.1-r2 or higher. !!! glibc-3.2.1-r2 ???? !!! <- well, there's no such thing, that's a typo in /usr/portage/profiles/default-sparc-1.0/packages isn't it guys? the users current versions are as mentioned; gcc-2.95.3-r7 <- correct glibs-2.2.5-r8 <- downrev due to typo? binutils-2.11.92.0.12.3-r2 <- downrev so, perhaps this means glibc will never update until the available version reaches 3.2.1 ? (unless I'm misinterpereting the profile package list) ok, that probably explains glibc not updating - someone who knows better will need to decide the latest stable glibc to fit the 1.0 profile and fix it. now let me think about binutils, for binutils we have the following ebuilds: x 2.11.92.0.7 x 2.11.92.0.12.3-r2 x 2.12.90.0.7 x 2.12.90.0.15 x 2.13.90.0.4 x 2.13.90.0.10 ~ 2.13.90.0.14 2.13.90.0.16 2.13.90.0.16-r1 2.13.90.0.18 ~ 2.13.90.0.18-r1 - 2.13.90.0.20 from the profile we know it must be binutils-2.13.90.0.14 or higher leaving 6 candidates, 3 of which are also masked in the ebuilds themselves. (I marked versions too low with a 'x', ~sparc masked versions with a '~', and blocked versions with a '-') leaving: 2.13.90.0.16 2.13.90.0.16-r1 2.13.90.0.18 we know 2.13.90.0.18 fails because of a patch, hence 2.13.90.0.18-r1 (which is masked), which leaves us with 2 viable ebuilds and 1 that could potentially cause trouble. (do we need to mask 2.13.90.0.18 ~ as well?) 2.13.90.0.16-r1 becomes our preferred candidate, I'm not quite sure how come you are not offered it. what happens if you attempt to `emerge -p /usr/portage/sys-devel/binutils/binutils-2.13.90.0.16-r1.ebuild` ? also, `emerge info` will confirm what profile you are using, portage version, etc.. which may help us confirm the problem oh, lastly, a later glibc will most likely fix the include problem you are having, I don't quite recall how long ago it was fixed but it's been a while now. (and at 1am I don't want to do too much more digging) :o)
I am sorry for the typo (glibs-2.2.5-r8), I read on a machine and type on another. I will triple check next time :^) Here are the versions I have: * sys-devel/gcc Latest version available: 2.95.3-r7 Latest version installed: 2.95.3-r7 * sys-libs/glibc Latest version available: 2.2.5-r8 Latest version installed: 2.2.5-r8 * sys-devel/binutils Latest version available: 2.11.92.0.12.3-r2 Latest version installed: 2.11.92.0.12.3-r2 I took the stage3 tarball from the 1.1a-r2 iso image and did a 'emerge sync' and 'emerge -u system'.
Ok, this problem has been reproduced on another sparc64 1.0 profile system. I locked pam-login to <=3.7 in "packages" of default-sparc64-1.0 (im CVS so please wait a bit before you report that emerge sync doesn't get it) For the reporter: It wont try to build 3.10 on your machine anymore with "emerge -u world". pam-login 3.10 is only for newer gentoo releases such as 1.4 on sparc64. The issue should be fixed but again. If you did a fresh installation on your machine i really suggest using 1.4. (1.0 is just a never touch a running system profile now)
limited pam-login version in profile 1.0 "packages" of sparc64
Closing
