Summary: | OpenLDAP 2.1.30-r1 fails compilation w/gcc "internal compiler error" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nick Veys <psylence519> |
Component: | New packages | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | preprocessed source output |
Description
Nick Veys
2004-08-28 19:03:00 UTC
Created attachment 38407 [details]
preprocessed source output
This occurred during a emerge -vuD world, and just before openldap came a new glibc and gcc: sys-libs/glibc-2.3.3.20040420-r1 sys-devel/gcc-3.3.4-r1 Not sure if they are the culprits, can't find any reference to this failure on the ole interwebnet exact same failure on 2.1.26 and 2.1.30-r3 I need your full 'emerge info' output as well as more of the error (specifically the actual GCC command that ran). If you have portage logging turned on, just attach all recent openldap compile logs. Well, in the mean time I downgraded to gcc-3.3.3-r6, tried again, and openldap-2.1.30-r1 compiles cleanly. Here is my 'emerge info' currently at gcc-3.3.3 (WORKING). I'll update gcc now and re-run but I imagine the difference in emerge info output is predictable there... How do I enable logging in portage, haven't done that yet, I'll do it and try to re-emerge openldap-2.1.30-r1 with the updated gcc and log the failure. Portage 2.0.50-r10 (default-x86-2004.2, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.6.7-gentoo-r11) ================================================================= System uname: 2.6.7-gentoo-r11 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirrors.tds.net/gentoo http://mirror.datapipe.net/gentoo http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apache2 apm arts avi berkdb cdr crypt encode foomaticdb gdbm gif gpm gtk2 imap imlib jpeg kde ldap libg++ libwww mad mikmod mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib" Can tell you that I had some problem too with openldap 2.1.30-r1 after I emerge -C ccache I could finally emerge openldap 2.1.30-r1 without a problem. just my 2 ct. if you had a problem like that with ccache, it sounds like you didn't clean out your ccache after upgrading major versions of gcc. Can't say I'd ever heard of ccache before this... Good to know though. nick: see your make.conf for logging Unfortunately due to unrelated problems with the main drive getting corrupted, I had to start fresh w/gentoo and am unable to reproduce this problem. May even attribute it to some drive problems, who knows. Sorry for wasting your time and thanks for the info. closing as WORKSFORME as user can't reproduce. |