emerge postgresql results in: ... make[2]: Entering directory `/var/tmp/portage/postgresql-8.0.1-r2/work/postgresql-8.0.1/src/port' powerpc64-unknown-linux-gnu-gcc -O2 -pipe -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wold-style-definition -Wendif-labels -fno-strict-aliasing -I../../src/port -DFRONTEND -I../../src/include -D_GNU_SOURCE -c -o crypt.o crypt.c -MMD crypt.c:240: error: parse error before "__int64" crypt.c:240: warning: no semicolon at end of struct or union crypt.c:242: warning: type defaults to `int' in declaration of `C_block' crypt.c:242: warning: data definition has no type or storage class crypt.c:296: error: parse error before '[' token crypt.c:299: error: parse error before "C_block" crypt.c: In function `permute': crypt.c:310: error: parse error before "C_block" crypt.c:311: warning: old-style parameter declaration crypt.c:315: error: `tp' undeclared (first use in this function) crypt.c:315: error: (Each undeclared identifier is reported only once crypt.c:315: error: for each function it appears in.) crypt.c:316: warning: ISO C90 forbids mixed declarations and code crypt.c:322: error: subscripted value is neither array nor pointer crypt.c:323: warning: left-hand operand of comma expression has no effect crypt.c:325: error: subscripted value is neither array nor pointer crypt.c:326: warning: left-hand operand of comma expression has no effect crypt.c:329: error: invalid type argument of `unary *' crypt.c:329: error: invalid type argument of `unary *' ... and so on several more. Reproducible: Always Steps to Reproduce: 1. emerge postgresql. (nothing in package.keywords or elsewhere to get anything other than the default blessed version) Actual Results: See the above 'Details'. Expected Results: Clean emerge. Gentoo Base System version 1.4.16 Portage 2.0.51.19 (default-linux/ppc64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6 ppc64) ================================================================= System uname: 2.6.11-gentoo-r6 ppc64 PPC970FX, altivec supported Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, May 1 2005, 23:22:55)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.90.0.3-r4 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="ppc64" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="powerpc64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://adelie.polymtl.ca/ ftp://cs.ubishops.ca/pub/gentoo ftp://gentoo.risq.qc.ca/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="X alsa apache2 arts berkdb bitmap-fonts cdr crypt cups curl dvd encode ethereal fam fortran gif gpm hardened imap jabber jack java jpeg kde ladcca mad motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam perl png postgres ppc64 python qt readline samba session sox speex spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode usb vorbis wifi xine xml2 xv zlib userland_GNU kernel_linux libc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
nigoro says this problem happens only on ppc64+hardened. reassigning..
Yes, that seems to be the case for two bugs I've recently submitted... I'm working on un-hardening, right now, to verify.
I've resolved this bug by un-hardening my machine. Shall we mark it resolved and/or completely pass on to the hardened team?
passing to hardened
Hardened PPC64 is not really complete. We lack of hardware for proper testing/debugging and q/a at this point in time. This is supposed to change sometime in the future. When that changes I'm happy to help resolve any bugs that is within my power to help resolve. Till then you will have to take the userland on a case by case basis and build what you can. If something does not build properly with +hardened features then sadly your probably better off switching to vanilla gcc specs via gcc-config for the package in question. Sorry all I can do at this point is resolve this bug as LATER
8.0 isn't in the tree. Doesn't get any later than this.
