This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
- From: Kai Tietz <Kai dot Tietz at onevision dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gcc at gcc dot gnu dot org, Tehila Meyzels <TEHILA at il dot ibm dot com>
- Date: Mon, 19 Feb 2007 13:13:15 +0100
- Subject: Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
Thank you very much. I solved this problem (of my absent-mindedness). When
I use the binaries install in /usr/local/bin everything works well 8).
Sorry and best regards,
i.A. Kai Tietz
Daniel Jacobowitz <drow@false.org>
19.02.2007 13:04
To
Kai Tietz <Kai.Tietz@onevision.com>
cc
Tehila Meyzels <TEHILA@il.ibm.com>, 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
> "--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
> tools defined. Under previous versions it worked. By the way, to make
the
> cross-compiler known via PATH would break my complete system.
That's not the one you want to run. You should have something in
/usr/local/bin/x86_64-pc-mingw32-gcc.exe also; do you?
The one in /usr/local/x86_64-pc-mingw32/bin is different, and may not
work - I think the way that normally happens involves symbolic links,
or something similar. Anyway, you don't need to use it.
--
Daniel Jacobowitz
CodeSourcery