This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Strange pathes for gcc for x86_64-pc-mingw32
- From: Andrew Haley <aph at redhat dot com>
- To: Kai Tietz <Kai dot Tietz at onevision dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Mon, 19 Feb 2007 10:24:35 +0000
- Subject: Re: Strange pathes for gcc for x86_64-pc-mingw32
- References: <OFC993B972.EB82BD22-ONC1257287.002DA83B-C1257287.002E9EF1@onevision.de>
[redirecting to gcc-help]
Kai Tietz writes:
> Hi,
>
> May somebody can explain me, the following case. I compiled a
> cross-complier for x86_64-pc-mingw32 and was successful on translare with
> the following build steps:
> 1. configure --target=x86_64-pc-mingw32
> 2. make all-gcc
> 3. make install-gcc
>
> But then I noticed, that the pathes to the tool-chain - which is installed
> under /usr/local/x86_64-pc-mingw32 - is used while compile, is somehow
> broken for the gcc tool. I assume, that the gcc toolchain is to be found
> under /usr/local/libexec/gcc/x86_64-pc-mingw32/4.3.0,
Should be in /usr/local/bin. Isn't it?
> but it is search in
> /usr/local/x86_64-pc-mingw32/libexec/x86_64-pc-mingw32/4.3.0. The
> make command "make install-gcc" installs the toolchain as expected
> under /usr/local/libexec/gcc/x86_64-pc-mingw32/4.3.0.
>
> Can me somebody help ? Is this a bug or normal behaviour ?
Andrew.