This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: PATCH: honor --oldincludedir
- To: <law at redhat dot com>
- Subject: RE: PATCH: honor --oldincludedir
- From: "Roger Collins" <roger at ProProject dot com>
- Date: Tue, 30 Jan 2001 10:43:53 -0500
- Cc: <gcc-patches at gcc dot gnu dot org>
I'm not sure what --with-include does, but the gcc/Makefile.in was using
/usr/include hard coded, not any config parameter.
Is there any reason to prefer --with-include over --oldincludedir? Is it a
naming convention thing?
Roger
> -----Original Message-----
> From: law@cygnus.com [mailto:law@cygnus.com]On Behalf Of Jeffrey A Law
> Sent: Thursday, January 25, 2001 6:11 PM
> To: Roger Collins
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: PATCH: honor --oldincludedir
>
>
>
> In message <3A704368.34280D34@proproject.com>you write:
> > All,
> >
> > I don't have write access to /usr/include and I wanted to fix
> something
> > there before running the build, so I copied /usr/include to my own
> > directory, made the fix, and used configure --oldincludedir=that-dir,
> > but the Makefile did not honor that config option. This patch fixes
> > that problem, I think. Please review.
> Can't you use --with-include= to do this instead?
>
> jeff
>
>