X-pop3-spooler: POP3MAIL 2.1.0 b 3 961213 -bs- Delivered-To: pcg AT goof DOT com From: nuke AT bayside DOT net X-Authentication-Warning: nuklear.steelcity.net: nuke owned process doing -bs Date: Tue, 3 Feb 1998 02:14:35 +0000 (GMT) X-Sender: nuke AT nuklear DOT steelcity DOT net To: pgcc list Subject: Re: pgcc-980129 compile problem In-Reply-To: <19980201202316.44348@cerebro.laendle> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Marc Lehmann Status: RO X-Status: A Content-Length: 1419 Lines: 38 > > i get this compiling the latest pgcc: > > I guess it is a redhat 5.0 system? (and may I guess this hapens with egcs > also?) nope, debian-hamm system.. based on glibc2 like redhat 5.0 > > > -lang-c -I. -I. -I./config -undef -D__GNUC__=2 -D__GNUC_MINOR__=7 > > -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix > > -D__linux -Asystem(posix) -D__OPTIMIZE__ -Di386 -Di586 -Asystem(unix) > > -Acpu(i386) -Amachine(i386) -D__i386__ -D__i586__ -Asystem(unix)__ > > -Acpu(i386)__ -Amachine(i386)__ __ __ __ __ __ __ > > __ __ __ __ __ __ __ __ -DIN_LIBGCC1 -DL_mulsi3 ./libgcc1.c > > /tmp/cca13517.i > > since your _installed_ gcc calls cpp with illegal args, this is most > probably a bug in the gcc you already have installed.. it might be that gcc > is searching for the wrong files (but I can only imagine the specs file) > > is it 2.7.2.3 from redhat? no: Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnu/pgcc-2.90.21/specs gcc version pgcc-2.90.21 971202 (egcs-1.00 release) > > those __'s aren't valid cpp options, and they're messing things up > > i really have no idea why it's doing this. > > Bad, I don't have either, although I would reaaly like to find > out why gcc is doing sth. that dumb, but I can't reproduce it! is there any place i should look for that? i'm guessing that it has something to do with this being a glibc2 system, and that not being detected right