This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: [mingw32] Make GCC work in any directory
- From: AWLaFramboise at aol dot com
- To: dannysmith at users dot sourceforge dot net (Danny Smith)
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 23 May 2003 03:31:45 -0400
- Subject: Re: PATCH: [mingw32] Make GCC work in any directory
In a message dated 5/23/2003 12:02:28 AM Eastern Standard Time, firstname.lastname@example.org writes:
[im assuming he meant to CC gcc-patches]
> ----- Original Message -----
> From: <AWLaFramboise@aol.com>
> To: "Danny Smith" <email@example.com>;
> Sent: Friday, 23 May 2003 02:57
> Subject: Re: PATCH: [mingw32] Make GCC work in any directory
> > In a message dated 5/22/2003 7:43:38 PM Eastern Standard Time,
> firstname.lastname@example.org writes:
> > > AWLaFramboise wrote:
> > > > Currently, GCC only works on MinGW if installed in particular
> > > > places. Due MinGW's filesystem having a slightly different
> > > > layout from most UNIX-like systems, GCC can't automatically
> > > > find certain things it needs, even with the MinGW-specific
> > > > relative path lookup thing.
> > > >
> ../gcc-3.3/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw
> 32 --
> target=mingw32 --prefix=/usr/local/share/gcc/gcc-3.3 --enable-threads --
> > -nls --enable-languages=c++,f77,objc --disable-win32-registry --disabl
> > --enable-sjlj-exceptions
> > DOES NOT work.
> Okay, normally I have the mingw runtime preinstalled in $(prefix). I
> use cygwin environment for building but with native gcc in front of
> cygwin's gcc.
> > Outside of this, perhaps it is a good idea to at least have
> > STANDARD_INCLUDE_DIR set correctly anyway? It seems like
> > this could minimize suprises, and it seems like a valid
> > setting would be better than something that is afaik completely
> > bogus now.
> It is bogus, but just changing that won't make a
Without dragging this silly issue out any more than necessary,
perhaps it would be best to commit both of these changes?
1) fixing STANDARD_INCLUDE_DIR and adding MD_STARTFILE_PREFIX
will make GCC work out of the box on a default modern mingw
install without having to copy around runtimes. speculating,
i think this will make --prefix work as expected, with the
least amount of suprises, for the most mingw users.
2) adding the auto-relative local-include snip, to
make --prefix work as smoothly as possible for people with
non-default configurations who are willing to make a copy
of the mingw runtime.
I see no downside to committing both mine and Danny's proposed
patch, and I think it will make the MinGW install a whole lot
more sensible for most users.
I understand CGF is the maintainer who would approve/commit
this? How does this sound to you?