This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Document exec and start file search behaviours.
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Carlos O'Donell <carlos at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, jsm at polyomino dot org dot uk, gerald at pfeifer dot com
- Date: Thu, 21 Dec 2006 22:10:01 -0800
- Subject: Re: [PATCH] Document exec and start file search behaviours.
- References: <20061221032425.GN14845@lios>
Carlos O'Donell wrote:
> This patch updates the documentation to reflect the reality of our exec
> and start file search behaviours.
@item
-The environment variable @code{GCC_EXEC_PREFIX}, if any.
+The environment variable @code{GCC_EXEC_PREFIX} or its automatically
determined
+value based on the installed toolchain location.
Better would be:
The environment variable @code{GCC_EXEC_PREFIX} or, if
@code{GCC_EXEC_PREFIX} is not set and the compiler has not
been installed in the configure-time prefix, the location
in which the compiler has actually been installed.
+The macro @code{STANDARD_EXEC_PREFIX}, but only if the toolchain is
installed
+in the configured @var{prefix} or this is a native compiler.
I don't think this is correct. I don't think native/cross has any
bearing on this, nor should it, since we're talking about programs the
compiler runs, not include directories searched. I think the actual
correct statement is:
The macro @code{STANDARD_EXEC_PREFIX}, if the compiler has been
installed in the configure-time prefix.
@item
-@file{/usr/lib/gcc/}.
+The location @file{/usr/lib/gcc/}, but only if this is a native compiler.
@item
-The macro @code{MD_EXEC_PREFIX}, if any.
+The location @file{/usr/libexec/gcc/}, but only if this is a native
compiler.
Reverse the order of these two, since we prefer /usr/libexec/gcc.
OK with those changes.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713