Fw: Strange paths for gcc for x86_64-pc-mingw32

Kai Tietz Kai.Tietz@onevision.com
Mon Feb 19 12:24:00 GMT 2007


Hi Andrew,

I tried it and setting the --prefix does not solve the problem. It still 
exists :(
But I did some debug prints at the place of gcc.c file, where the 
gcc_libexec_prefix is build by make_relative_prefix() and saw that the 
path problem is resulting there.
The content before calling of argv[0] is 
/usr/local/x86_64-pc-mingw32/bin/gcc
The content before calling of standard_bindir_prefix is /usr/local/bin
The content before calling of standard_libexec_prefix is 
/usr/local/libexec/gcc
The result of these pathes for gcc_libexec_prefix is than 
/usr/local/x86_64-pc-mingw32/bin/../libexec/gcc

Regards,
 i.A. Kai Tietz





Andrew Haley <aph@redhat.com> 
19.02.2007 11:29

To
Kai Tietz <Kai.Tietz@onevision.com>
cc
Tehila Meyzels <TEHILA@il.ibm.com>, gcc-help@gcc.gnu.org
Subject
Re: Fw: Strange paths for gcc for x86_64-pc-mingw32






Kai Tietz writes:
 > 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.

Ah, OK, now you explain the real problem.  If you build it with
--prefix=, does that work?

Andrew.





More information about the Gcc-help mailing list