Mail Archives: pgcc/1998/02/02/18:32:32
> > 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
- Raw text -