Hi,
Thank you for the answer Kai. My comments below
2011/10/28 Kai Tietz <[email protected]>
> The issue is that you are setting PATH to wrong bin directory. You
> should use here 'c:\s2e\s2e-toolchain\mingw64\bin' instead. The
> folder 'c:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\bin' is for
> internal use only and has not to be used by user directly.
>
Indeed, it apparently do something. But I think my set up is not correct.
since I built gcc 4.7.0 with gcc 4.6.1, I have both installed on my machine.
And of course the default one is 4.6.1 whereas I want the other one.
with the PATH you told me to set up, I have what is reported below. Where
can I learn about the internal of the directory structure so that I can
configure my gcc appropriately. In the user manual, this is not that clear
actually?
Alexandre.
-----------------------------------------------------------------8<-----------------------------------------------------------------------------
$ which gcc
/mingw64/bin/gcc.exe
$ gcc -v
Using built-in specs.
COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\gcc.exe
COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure
--host=x86_64-w64-mingw32 --target=x86_64-w6
4-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++
--with-gmp=/home/drangon/work/mingw-w64-dgn/build/for
_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry
--prefix=/home/drangon/work/mingw-w64-
dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target
Thread model: win32
gcc version 4.6.1 20110417 (prerelease) (GCC)
$ which x86_64-w64-mingw32-gcc.exe
/mingw64/bin/x86_64-w64-mingw32-gcc.exe
$ x86_64-w64-mingw32-gcc.exe -v
-> pop up saying libintl-8.dll is missing, but actually it is not missing,
it is just the set up which is messed up.
$ x86_64-w64-mingw32-gcc-4.7.0.exe -v
-> pop up saying libintl-8.dll is missing, but actually it is not missing,
it is just the set up which is messed up.
$ x86_64-w64-mingw32-gcc-4.6.1.exe -v
Using built-in specs.
COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\x86_64-w64-mingw32-gcc-4.6.1.exe
COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure
--host=x86_64-w64-mingw32 --target=x86_64-w6
4-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++
--with-gmp=/home/drangon/work/mingw-w64-dgn/build/for
_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry
--prefix=/home/drangon/work/mingw-w64-
dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target
Thread model: win32
gcc version 4.6.1 20110417 (prerelease) (GCC)
$ which x86_64-w64-mingw32-gcc-4.7.0.exe
/mingw64/bin/x86_64-w64-mingw32-gcc-4.7.0.exe
--
Alexandre
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
