Re: --without-local-prefix Does Not Work

[Vin Shelton <acs at alumni dot princeton dot edu>]

I was wrong.  The configure option --with-local-prefix=no does not work.
After running configure with this option I still end up with a gcc/Makefile
which includes the definition:

local_prefix = /usr/local

This causes /usr/local/include to be in the list of automatically searched 
directories, as if a -I/usr/local/include had been added to the command 
line.

Short of hand-editing gcc/Makefile (which I'm now doing), how can I run 
configure so that it doesn't generate that line.  I don't want my compiler 
to do anything special with /usr/local/include, thank you very much.

I had written:
>     If --without-local-prefix is no longer going to work, that's OK, but 
> it represents a change in behavior.  As I mentioned, as recently as the 7/27 
> snapshot it worked the way I expected, which was:
> 	--with-local-prefix=/foo/bar	- local includes are in /foo/bar
> 	--without-local-prefix		- don't default to any local includes
> 	or nothing, which was the same as --with-local-prefix=/usr/local.
> I've been building --without-local-prefix for quite awhile.
> Looking at configure, at a guess I think I can say --with-local-prefix=
> "some-non-existant-path" to get the old behavior.
> 
> thanks,
>   vin shelton
> 
>   In message <199808162235.SAA03053@spacely.icd.teradyne.com>I had written:
>   > The configure option '--without-local-prefix' has not worked in either
>   > of the 2 most recent snapshots, 08/03 or 08/16.  It worked successfully
>   > on the 07/27 snapshot.  The gcc/Makefile generated from these snapshots
>   > contains the following line:
> 
> law@hurl.cygnus.com said:
> > The -local-prefix options are meant to be passed a pathname.  They are
> > not yes/no options. 
> 
> 
>