On 29 Mar 2001, at 17:43, the Illustrious Paul Sokolovsky wrote:
> Hello Georg,
> Georg Fusz <fusz@...> wrote:
> GF> There are also some other problems with finding the header-files.
> GF> It would be very nice, if one of the maintainer of MinGw could
> GF> 1. How does 'gcc' or 'cc1' find the directories with the standard
> GF> [Where can I read about this subject?]
> In the output of "gcc -v foo.c", where else?
> GF> Sorry, but the only thing I know, ist, that the environment var
> PATH, is only GF> for finding executables.
> There are environment variables which do control where gcc
> searches for its stuff. You SHOULD NOT have them set. Which are they?
> RTFM. Example is GCC_EXEC_PREFIX (the place where look for frontends,
> etc). So I suspect that some of the problems reported are due to those
> variables being set (by some other package).
Exactly. GCC_EXEC_PREFIX is a predefeind Env Var. It should not ever
need to be changed except in very specific circumstances...perhaps it
was not made clear...
GCC_EXEC_PREFIX is a predefined Env Var with, afaik, "all" GCC based
compilers. It tells whichever shell you are using (cmd.exe or
command.exe, bash, etc.) where c/c++ executables (c++.exe/gcc.exe) need
to look (for cygwin that is a mount list which includes the necessary
headers, for mingw that is a specific set of paths, including the
headers) when they (gcc/g++) are attempting to build (Compile And Link)
If you are using Mingw and Cygwin as Separate Development Tool Sets.
(Which contrary to what appears to be popular belief, is in fact,
true)...if you do not inform your mingw and cygwin bat files where
their gcc_exec_prefix (a pointer to the compiler specs file) should be,
they will assume the installation default...the default in every case,
unless you specifically state otherwise, will always point to the last
valid specs file that gcc should be using.
If, on the other hand you are using Cygwin gcc -mno-cygwin, then
GCC_EXEC_PREFIX has already been defined and you are requred to "leave
it alone" if you want your Cygwin builds to work.
GCC_EXEC_PREFIX, under Mingw should not ever be changed, period. What
few exceptions exist, in the case of Mingw, are only applicable if you
have multiple copies of mingw on your system, and each copy is expected
to be a single stand-alone development tool set which _needs to run
concurrently_ with other instances of the Mingw Development Tools.
> GF> 2. Why was the file-structure changed since Mumit's installations?
> There was long talk (and discussion) about this.
(Which Mumit agreed was a good re-definition after reviewing the new
> Resume: for ease
> and consistency. Default target of mingw
> was agreed to be 'mingw32' (so,
> you're supposed to do ./configure --host=mingw32 to build mainstream
> mingw stuff (i.e. ix86/msvcrt)). So, I patched gcc distro to adhere to
> this convention.
Nothing real can be threatened.
Nothing unreal exists.