Re: gcc 2.95{,.1} looping forever

[CaT <cat at zip dot com dot au>]

On Thu, Aug 19, 1999 at 08:07:52PM -0700, Zack Weinberg wrote:
> CaT wrote:
> > On Thu, Aug 19, 1999 at 05:10:23PM -0600, Jeffrey A Law wrote:
> > >   In message <199908191905.PAA22196@qnx.com>you write:
> > >   > > 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
> > > NO, $prefix/bin.  It is a CPP that is user-visible.  The one in
> > > $prefix/lib/gcc-lib/$target/$version/cpp is *NOT* supposed to be
> > > directly called.
> > 
> > Ok. Kinda sorta related question... XFree wants a cpp in /lib. do I
> > softlink /lib/cpp to $prefix/bin/cpp or
> > $prefix/lib/gcc-lib/$target/$version/cpp?
> > 
> > Currently I use the latter but this msg has made me pause and think...
> 
> $(prefix)/bin/cpp.

Thanks.

> I'm starting to wonder if we shouldn't rename gcc-lib/T/V/cpp to cpp1
> or something like that - it would get rid of the confusion, and the
> infinite loop.  The specs changes required might be messy though.

It'd be an idea... though I don't quite remember why I chose the 
gcc-lib/T/V/cpp on over the pref/bin/cpp one...

weird.

-- 
CaT (cat@zip.com.au)                       URL: http://www.zip.com.au/dev/null