[Mingw-w64-public] 4 compiler issues

2010-05-14 Thread Jim Michaels
1. I have noticed that for sezero and auto compilers, there averages 7-8 LONG directories for lib path totalling 284-328 characters 5 LONG directories for include path totalling 274-310 characters 1-2 directories for bin path. I suggest at least a .cmd batch file to set the paths and environmen

Re: [Mingw-w64-public] suggestion

2010-05-14 Thread JonY
On 5/15/2010 11:34, Jim Michaels wrote: > one easy thing you could include with the compiler is a batch file which sets > the environment variables for the compiler. put it in the bin directory for > consistency. > > the variables that need to be set (I think) at least, are > OBJC_INCLUDE_PATH >

[Mingw-w64-public] suggestion

2010-05-14 Thread Jim Michaels
one easy thing you could include with the compiler is a batch file which sets the environment variables for the compiler. put it in the bin directory for consistency. the variables that need to be set (I think) at least, are OBJC_INCLUDE_PATH C_INCLUDE_PATH INCLUDE_PATH CPATH CPLUS_INCLUDE_PATH

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Tony Theodore
On 15 May 2010 05:28, Doug Semler wrote: > 2010/5/14 Tony Theodore : >> 2010/5/15 Mario Rodríguez : >>> Hi, >>> >>> I want to use *MKL*`s lapack & BLAS in my *mingw* project. >>> >>> I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, >>> mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 3

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Kai Tietz
2010/5/14 Mario Rodríguez : > Kai Tietz wrote: >> >> 2010/5/14 Tony Theodore : >> >>> >>> 2010/5/15 Mario Rodríguez : >>> Hi, I want to use *MKL*`s lapack & BLAS in my *mingw* project. I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, mkl_intel_thread

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Mario Rodríguez
Kai Tietz wrote: > 2010/5/14 Tony Theodore : > >> 2010/5/15 Mario Rodríguez : >> >>> Hi, >>> >>> I want to use *MKL*`s lapack & BLAS in my *mingw* project. >>> >>> I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, >>> mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 32b arquitect

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Kai Tietz
2010/5/14 Tony Theodore : > 2010/5/15 Mario Rodríguez : >> Hi, >> >> I want to use *MKL*`s lapack & BLAS in my *mingw* project. >> >> I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, >> mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 32b arquitecture, it´s >> enought adding this files

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Doug Semler
2010/5/14 Tony Theodore : > 2010/5/15 Mario Rodríguez : >> Hi, >> >> I want to use *MKL*`s lapack & BLAS in my *mingw* project. >> >> I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, >> mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 32b arquitecture, it´s >> enought adding this files

Re: [Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Tony Theodore
2010/5/15 Mario Rodríguez : > Hi, > > I want to use *MKL*`s lapack & BLAS in my *mingw* project. > > I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, > mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 32b arquitecture, it´s > enought adding this files names at the end of the g++ linking

[Mingw-w64-public] Mingw + mkl

2010-05-14 Thread Mario Rodríguez
Hi, I want to use *MKL*`s lapack & BLAS in my *mingw* project. I use this libraries for 32 bits linking: mkl_intel_c_dll.lib, mkl_intel_thread_dll.lib, mkl_core_dll.lib. In 32b arquitecture, it´s enought adding this files names at the end of the g++ linking line. But in 64 bits (using mingw-w6

[Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-05-13)

2010-05-14 Thread Ozkan Sezer
To anyone who might be interested: I updated my custom w32/w64 native and cross-compiler build with gcc-4.4 with several backports and fixes from mainstream and put them under the mingw-w64 sf.net file release system under the subdirectories: - Toolchain sources -> Personal Builds, - Toolchains t