[Bug driver/21553] GCC_EXEC_PREFIX mechanism is broken

["roche at act-europe dot fr" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From roche at act-europe dot fr  2005-05-13 23:40 -------
Subject: Re:  GCC_EXEC_PREFIX mechanism is broken

pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-13 22:53 -------
> If I read the docs correctly it says you have to add -B. to the invocation.
> 

As far as I understand, you can add -B but you don't have to.
(from the docs)
"If GCC_EXEC_PREFIX is set, it specifies a prefix to use in the names of 
the subprograms executed by the compiler"

"Other prefixes specified with -B take precedence over this prefix"

> See PR 19856 and 14435.
> 
> Reference from the docs:
> In addition, the prefix is used in an unusual way in finding the directories to search for header files. For 
> each of the standard directories whose name normally begins with /usr/local/lib/gcc (more precisely, 
> with the value of GCC_INCLUDE_DIR), GCC tries replacing that beginning with the specified prefix to 
> produce an alternate directory name. Thus, with -Bfoo/, GCC will search foo/bar where it would 
> normally search /usr/local/lib/bar. These alternate directories are searched first; the standard 
> directories come next. 
> 

I am sorry but I don't understand your comment. This paragraph of the 
documentation concerns the header files and not programs like cc1 ...

Is there something I miss ?

Futhermore the documentation says:
The default value of GCC_EXEC_PREFIX is prefix/lib/gcc/ where prefix is 
the value of prefix when you ran the configure script.

If you set explicitely the value of GCC_EXEC_PREFIX to this default, the 
driver do not behave the same way. (basically it will look first in 
prefix/../libexec/gcc/<target>/<version> instead of 
prefix/libexec/gcc/<target>/<version> for programs).

Best regards,
Nicolas



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21553