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-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, 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 ? You're writing that the toolchain is installed under /usr/local/x86_64-pc-mingw32, but you assume it should be under /usr/local/libexec/gcc/x86_64-pc-mingw32/. Why? If you want it to be under /usr/local/libexec/gcc/x86_64-pc-mingw32/, you should configure with --prefix=/usr/local/libexec/gcc. In case you just need it to find it in the correct place (i.e., /usr/local/libexec/gcc/x86_64-pc-mingw32/4.3.0), you need to put it at the beginning of your $PATH. (check what you have there with "echo $PATH" and then use setenv/export). HTH, Tehila. > > Regards, > i.A. Kai Tietz > > ---------------------------------------- > Kai Tietz - Software engineering > OneVision Software Entwicklungs GmbH & Co KG > Dr.-Leo-Ritter-Str. 9, 93049 Regensburg, Germany > Phone: +49-941-78004-0 > FAX: +49-941-78004-489 > WWW: http://www.OneVision.com
