This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc and include dirs
- From: "Gerold J. Wucherpfennig" <gjwucherpfennig at gmx dot net>
- To: mszick at goquest dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 1 Mar 2003 22:21:14 +0100
- Subject: Re: gcc and include dirs
- References: <200302280819.41504.gjwucherpfennig@gmx.net> <200303010040.19558.gjwucherpfennig@gmx.net> <03022818413400.31663@wolf466>
On Saturday March 1 2003 01:41, Michael S. Zick wrote:
> On Friday 28 February 2003 05:40 pm, Gerold J. Wucherpfennig wrote:
> > On Friday February 28 2003 17:56, Michael S. Zick wrote:
> > > On Friday 28 February 2003 09:43 am, Gerold J. Wucherpfennig wrote:
> >
> > The only (but not really) "clean" solution I can imagine is to
> > - fix gcc to look into /opt/*/include,
> > - fix ld to look into /opt/*/lib
> > - fix bash to look into /opt/*/bin and /opt/*/sbin
> > - fix man to look into /opt/*/man
> > - fix info to look into /opt/*/info
> > - ...
>
> That will be a hard sell.
> The convention in the *nix system world is for the
> command shell to do all wildcard expansions, not
> the individual programs.
Yes indeed, GCC and CO. can't use shell wildcards.
They have to examine the dirs in /opt and (maybe) cache the results!
(I just used wildcards to to make it easy to understand.)
What do others think about this proposual?
(Alternatively GCC and CO. could use configuration files like ld.so.conf)
IMHO there has to be a "clean" solution to this "/opt" issue.
Please CC me
Gerold