t;
cc
Tehila Meyzels <[EMAIL PROTECTED]>, gcc@gcc.gnu.org
Subject
Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
On Mon, Feb 19, 2007 at 10:35:41AM +0100, Kai Tietz wrote:
> Hi,
>
> No the point is that I am using the default settings of gcc (without any
> "--p
On Mon, Feb 19, 2007 at 10:35:41AM +0100, Kai Tietz wrote:
> Hi,
>
> No the point is that I am using the default settings of gcc (without any
> "--prefix="). The compiler is built and installed at the expected place
> (/usr/local/libexec/gcc/...), but the gcc,exe tool installed under
> /usr/loc
Hi,
No the point is that I am using the default settings of gcc (without any
"--prefix="). The compiler is built and installed at the expected place
(/usr/local/libexec/gcc/...), but the gcc,exe tool installed under
/usr/local/x86_64-pc-mingw32/bin does not have the proper path to its gcc
tool
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, but it is search in
/
Kai Tietz wrote on 19/02/2007 10:29:13:
> 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
