gcc 2.95{,.1} looping forever
Alain Magloire
alain@qnx.com
Thu Aug 19 12:06:00 GMT 1999
>
> On Wed, 18 Aug 1999, Alain Magloire wrote:
> > Bonjour
> >
> > # GCC_EXEC_PREFIX=/usr/local/ gcc -v c.c
> > ....
> > ##
> >
> > will put the driver in looping mode when using the builtin specs.
> > There is nothing particular about "/usr/local" any path will do.
> >
>
> I guess You used --prefix=/usr/local (default) when configured gcc-2.95.
No --prefix=/opt/local
> The the reason is simple:
>
> gcc-2.95 installs preprocessor executeble in $prefix/bin (it's
> different from cpp used by gcc itself. If You specify
You mean $prefix/lib/gcc-lib/$target/$version/cpp
> GCC_EXEC_PREFIX=/usr/local gcc errorously finds
> wrong cpp executable which tries recursively to call itself.
> I had the same problem for target=i586-pc-msdosdjgpp when
> similar GCC_EXEC_PREFIX were used (Tested, it happens also
> in Linux, I had prefox=/usr though)
Ok, thanks for the explanation, It will also happen if you do
# uname -sr
SunOS 5.6
# GCC_EXEC_PREFIX=/usr/ gcc -v c.c
Using builtin specs.
gcc version 2.95 19990728 (release)
cpp -lang-c -v -iprefix ......
...
looping forever
...
^C
# which cpp
/usr/local/bin/cpp
#
--
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!
More information about the Gcc-bugs
mailing list