This is the mail archive of the
mailing list for the GCC project.
Re: [MinGW] Set NATIVE_SYSTEM_HEADER_DIR relative to configured prefix
- From: 'Bob Rossi' <bob_rossi at cox dot net>
- To: Danny Smith <dannysmith at clear dot net dot nz>
- Cc: 'Ranjit Mathew' <rmathew at gmail dot com>, 'GCC Patches' <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 19 Dec 2006 08:53:54 -0500
- Subject: Re: [MinGW] Set NATIVE_SYSTEM_HEADER_DIR relative to configured prefix
- References: <20061218131509.GW20942@cox.net> <004201c7232e$74941cc0$7d6d65da@anykey>
On Tue, Dec 19, 2006 at 06:27:58PM +1300, Danny Smith wrote:
> Bob Rossi
> Tuesday, 19 December 2006 2:15 a.m.
> > Hi Ranjit,
> > Thanks for your response. It doesn't look like Danny was building a
> > relocatable gcc for mingw. It doesn't seem like anyone that reads the
> > gcc, gcc-patches or mingw-users list knows how either.
> Can you please explain what you mean by 'relocateable'? GCC has been
> relocateable on mingw target for a long time (since 1999 at least).
> That is, GCC_EXEC_PREFIX is determined relative to the gcc driver. To
> work, the directory containing the gcc driver must be in $PATH.
OK. I'm sorry. I'm making assumptions. I'm starting to get a bigger
picture of how to do what I need to. I thought that --sysroot was needed
in order to make gcc relocatable, but apparently that's not true. Daniel
and Brian and now told me that gcc should always be relocatable.
> Eg, I can relocate the whole mingw toolchain from c:/mingw to
> any_other_directory and it will still work as long as
> any_other_directory is in $PATH.
OK, that's great to know. What's frustrating is, each different build of
gcc I do on mingw has slightly different compile errors and slightly
different behaviors. Now that I'm starting to get the big picture, I
maybe be able to send in more meaningful bug reports.