Re: [Mingw-w64-public] Did anyone got TBB 2.2 to build with mingw64 before?

2010-09-20 Thread Hradec
That fixed the warning, but I'm still getting the same errors: i686-w64-mingw32-g++ -c -MMD -g -O0 -DTBB_USE_DEBUG -DUSE_WINTHREAD -D__MSVCRT_VERSION__=0x0700 -msse -mthreads -m32-fno-rtti -fno-exceptions -D__TBB_BUILD=1 -Wno-parentheses -I../../src -I../../include -I../../src/tbbmalloc -I../

Re: [Mingw-w64-public] Did anyone got TBB 2.2 to build with mingw64 before?

2010-09-20 Thread Dongsheng Song
On 2010-9-21 10:26, Dongsheng Song wrote: > On 2010-9-21 10:11, Hradec wrote: >> I got tbb.dll to build properly, but its failling when building tbbmalloc: >> >> >> ../../src/tbbmalloc/MemoryAllocator.cpp:42:0: warning: "_WIN32_WINNT" >> redefined >> /media/MyBook2TB_2/Mirror/cortex4all/trunk/co

Re: [Mingw-w64-public] Did anyone got TBB 2.2 to build with mingw64 before?

2010-09-20 Thread Dongsheng Song
On 2010-9-21 10:11, Hradec wrote: > I got tbb.dll to build properly, but its failling when building tbbmalloc: > > > ../../src/tbbmalloc/MemoryAllocator.cpp:42:0: warning: "_WIN32_WINNT" > redefined > /media/MyBook2TB_2/Mirror/cortex4all/trunk/compilers/linux.mingw32.4.6.0_20100411/bin/../lib/gcc

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Xiaofan Chen
On Tue, Sep 21, 2010 at 8:27 AM, JonY wrote: >>> Long time reader of this discussion :) >>> Why not just add this to the bottom/top of libusb's usb.h header: >>> #ifdef __MINGW64_VERSION_MAJOR     #include_next #endif // __MINGW64_VERSION_MAJOR Actually it is not libusb-w

[Mingw-w64-public] Did anyone got TBB 2.2 to build with mingw64 before?

2010-09-20 Thread Hradec
I got tbb.dll to build properly, but its failling when building tbbmalloc: ../../src/tbbmalloc/MemoryAllocator.cpp:42:0: warning: "_WIN32_WINNT" redefined /media/MyBook2TB_2/Mirror/cortex4all/trunk/compilers/linux.mingw32.4.6.0_20100411/bin/../lib/gcc/i686-w64-mingw32/4.6.0/../../../../i686-w64-m

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread JonY
On 9/21/2010 07:53, Xiaofan Chen wrote: > On Mon, Sep 20, 2010 at 10:30 PM, Ruben Van Boxem > wrote: >> 2010/9/20 JonY >>> OK, I see. I suppose some include_next tricks are in order for libusb. >>> >> >> Long time reader of this discussion :) >> Why not just add this to the bottom/top of libusb's

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Xiaofan Chen
On Mon, Sep 20, 2010 at 10:30 PM, Ruben Van Boxem wrote: > 2010/9/20 JonY >> OK, I see. I suppose some include_next tricks are in order for libusb. >> > > Long time reader of this discussion :) > Why not just add this to the bottom/top of libusb's usb.h header: > >> #ifdef __MINGW64_VERSION_MAJOR

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread Andy Koppe
On 20 September 2010 15:39, JonY wrote: >> On Mon, Sep 20, 2010 at 10:28 AM, JonY wrote: >>> Will 64bit Cygwin be LP64 or LLP64? I sure hope its the former, but I >>> don't know how much thunk is needed. Interesting question. No idea what the answer is, but I guess LP64 would mean LONG == int and

Re: [Mingw-w64-public] GMP 5.0.1 and i686-w64-mingw32 and

2010-09-20 Thread Ruben Van Boxem
2010/9/20 Ozkan Sezer > > [...] > conftest.c:129:48: error: /home/Ruben/mingw64/src/gmp/gmp-h.in: No > such file or directory > conftest.c: In function 'longval': > conftest.c:132: error: 'mp_limb_t' undeclared (first use in this function) > conftest.c:132: error: (Each undeclared identifier is r

Re: [Mingw-w64-public] GMP 5.0.1 and i686-w64-mingw32 and

2010-09-20 Thread Ozkan Sezer
On Mon, Sep 20, 2010 at 6:33 PM, Ruben Van Boxem wrote: > Hi, > > In an attempt to run my build script for an i686 build, I ran into trouble > when configuring GMP 5.0.1. > > I'm using sezero's latest mingw-w32 build and it's the only compiler in my > PATH. > > Attached are the config.log and the

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread Ruben Van Boxem
2010/9/20 NightStrike > On Mon, Sep 20, 2010 at 10:39 AM, JonY > wrote: > > On 9/20/2010 22:53, NightStrike wrote: > >> > >> On Mon, Sep 20, 2010 at 10:28 AM, JonY > >> wrote: > >>> > >>> On 9/20/2010 22:36, Earnie wrote: > > Kai Tietz wrote: > > > > 2010/9/20 Earnie: > >>

Re: [Mingw-w64-public] rubenvb Personal Build

2010-09-20 Thread NightStrike
Wonderful, thanks! On Mon, Sep 20, 2010 at 11:26 AM, Ruben Van Boxem wrote: > 2010/9/20 NightStrike >> >> Did you upload this to the sourceforge file release area under Personal >> Builds? >> > > I sure did: > > x64 binary: > https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetti

Re: [Mingw-w64-public] rubenvb Personal Build

2010-09-20 Thread Ruben Van Boxem
2010/9/20 NightStrike > Did you upload this to the sourceforge file release area under Personal > Builds? > > I sure did: x64 binary: https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/ source with x64 build script: https://sourceforge.net

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread NightStrike
On Mon, Sep 20, 2010 at 10:39 AM, JonY wrote: > On 9/20/2010 22:53, NightStrike wrote: >> >> On Mon, Sep 20, 2010 at 10:28 AM, JonY >>  wrote: >>> >>> On 9/20/2010 22:36, Earnie wrote: Kai Tietz wrote: > > 2010/9/20 Earnie: >> >> Cesar Strauss wrote: >>> >>> Since

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread JonY
On 9/20/2010 22:53, NightStrike wrote: > On Mon, Sep 20, 2010 at 10:28 AM, JonY wrote: >> On 9/20/2010 22:36, Earnie wrote: >>> Kai Tietz wrote: 2010/9/20 Earnie: > Cesar Strauss wrote: >> >> Since MSYS is derived from Cygwin, one way to get 64-bit support >> for MSYS would be

Re: [Mingw-w64-public] rubenvb Personal Build

2010-09-20 Thread NightStrike
Did you upload this to the sourceforge file release area under Personal Builds? On Mon, Sep 20, 2010 at 8:07 AM, Ruben Van Boxem wrote: > Hi everyone, > > I completed my first good GCC build with mingw-w64. It uses GCC 4.5.2, > binutils 2.20.51 and mingw-w64 snapshots from 2010-09-16. The script

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread NightStrike
On Mon, Sep 20, 2010 at 10:28 AM, JonY wrote: > On 9/20/2010 22:36, Earnie wrote: >> Kai Tietz wrote: >>> 2010/9/20 Earnie: Cesar Strauss wrote: > > Since MSYS is derived from Cygwin, one way to get 64-bit support > for MSYS would be to add it first to Cygwin and port it to MSYS >

Re: [Mingw-w64-public] multiple definition of _encode_pointer/_decode_pointer

2010-09-20 Thread Dongsheng Song
On Mon, Sep 20, 2010 at 18:50, Ozkan Sezer wrote: > On Mon, Sep 20, 2010 at 12:32 PM, Dongsheng Song > wrote: > > Hi all, > > > > When I compile cx_Oracle, I got the warn/error: > > > > O:\gcc-4.5-w32\bin\gcc.exe -mno-cygwin -shared -s > > build\temp.win32-2.6-11g\Release\cx_oracle.o > > build\t

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread JonY
On 9/20/2010 22:36, Earnie wrote: > Kai Tietz wrote: >> 2010/9/20 Earnie: >>> Cesar Strauss wrote: Since MSYS is derived from Cygwin, one way to get 64-bit support for MSYS would be to add it first to Cygwin and port it to MSYS later. However, as this thread indicates, there is

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread Earnie
Kai Tietz wrote: > 2010/9/20 Earnie : >> Cesar Strauss wrote: >>> >>> Since MSYS is derived from Cygwin, one way to get 64-bit support >>> for MSYS would be to add it first to Cygwin and port it to MSYS >>> later. However, as this thread indicates, there is currently some >>> interest on bringing 6

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Ruben Van Boxem
2010/9/20 JonY > On 9/20/2010 22:09, Ozkan Sezer wrote: > > On Mon, Sep 20, 2010 at 4:40 PM, JonY > wrote: > >> On 9/20/2010 21:36, Earnie wrote: > >>> Forgot to include the list. > >>> > >>> Original Message > >>> Message-ID:<4c976081.6090...@users.sourceforge.net> > >>> Date:

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread JonY
On 9/20/2010 22:09, Ozkan Sezer wrote: > On Mon, Sep 20, 2010 at 4:40 PM, JonY wrote: >> On 9/20/2010 21:36, Earnie wrote: >>> Forgot to include the list. >>> >>> Original Message >>> Message-ID:<4c976081.6090...@users.sourceforge.net> >>> Date: Mon, 20 Sep 2010 09:24:17 -040

Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Xiaofan Chen
On Mon, Sep 20, 2010 at 9:57 PM, Ozkan Sezer wrote: > On Mon, Sep 20, 2010 at 4:03 PM, Xiaofan Chen wrote: >> In this case, MinGW is actually following MS side, and not MinGW-w64, >> Even Kai Tietz admits that MinGW-w64 usb.h belongs to DDK. It is just >> because of the convenience (to support w

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Ozkan Sezer
On Mon, Sep 20, 2010 at 4:40 PM, JonY wrote: > On 9/20/2010 21:36, Earnie wrote: >> Forgot to include the list. >> >> Original Message >> Message-ID:<4c976081.6090...@users.sourceforge.net> >> Date:     Mon, 20 Sep 2010 09:24:17 -0400 >> From:     Earnie >> User-Agent:     Mozill

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread Kai Tietz
2010/9/20 Earnie : > Cesar Strauss wrote: >> >> Since MSYS is derived from Cygwin, one way to get 64-bit support for >>  MSYS would be to add it first to Cygwin and port it to MSYS later. >> However, as this thread indicates, there is currently some interest >> on bringing 64-bit support to MSYS, w

Re: [Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread JonY
On 9/20/2010 21:36, Earnie wrote: > Forgot to include the list. > > Original Message > Message-ID:<4c976081.6090...@users.sourceforge.net> > Date: Mon, 20 Sep 2010 09:24:17 -0400 > From: Earnie > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; > rv:1.9.1.13

Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Ozkan Sezer
On Mon, Sep 20, 2010 at 4:03 PM, Xiaofan Chen wrote: > On Mon, Sep 20, 2010 at 8:50 PM, Earnie wrote: >> Ozkan Sezer wrote: >>> Mingw has not been updating their ddk for years and certainly they >>> don't reflect the changes is directory structure from the MS side: >>> mingw does not define the a

[Mingw-w64-public] Fwd: Re: libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Earnie
Forgot to include the list. Original Message Message-ID: <4c976081.6090...@users.sourceforge.net> Date: Mon, 20 Sep 2010 09:24:17 -0400 From: Earnie User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.13) Gecko/20100914 SeaMonkey/2.0.8 MIME-Versi

Re: [Mingw-w64-public] MSYS-64 team

2010-09-20 Thread Earnie
Cesar Strauss wrote: > > Since MSYS is derived from Cygwin, one way to get 64-bit support for > MSYS would be to add it first to Cygwin and port it to MSYS later. > However, as this thread indicates, there is currently some interest > on bringing 64-bit support to MSYS, while I do not have evidenc

Re: [Mingw-w64-public] MSYS-64

2010-09-20 Thread Earnie
ArbolOne wrote: > Ok, folks. Apparently no one else is jumping on the Build MSYS under 64bit > MSWin waggon. So, let us start with the project. > Does any of you know where to get the latest source code? > > MSYS-64 Development Team > ~~ > Teemu > Bidski > NightStrike > Luis

Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Kai Tietz
2010/9/20 Earnie : > Ozkan Sezer wrote: >> On Sun, Sep 19, 2010 at 2:03 PM, Xiaofan Chen >> wrote: >>> On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer >>> wrote: > However, MinGW does not break existing software and puts those > files inside include\ddk sub-directory. Why not MinGW-w64?

Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Xiaofan Chen
On Mon, Sep 20, 2010 at 8:50 PM, Earnie wrote: > Ozkan Sezer wrote: >> Mingw has not been updating their ddk for years and certainly they >> don't reflect the changes is directory structure from the MS side: >> mingw does not define the api or directory structure, ms does. >> >> I think we put eve

Re: [Mingw-w64-public] libusb-win32 usb.h and MinGW-w64 usb.h conflict

2010-09-20 Thread Earnie
Ozkan Sezer wrote: > On Sun, Sep 19, 2010 at 2:03 PM, Xiaofan Chen > wrote: >> On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer >> wrote: However, MinGW does not break existing software and puts those files inside include\ddk sub-directory. Why not MinGW-w64? >>> >>> What will happen to oth

[Mingw-w64-public] rubenvb Personal Build

2010-09-20 Thread Ruben Van Boxem
Hi everyone, I completed my first good GCC build with mingw-w64. It uses GCC 4.5.2, binutils 2.20.51 and mingw-w64 snapshots from 2010-09-16. The script used to build the binary package is included in the source download. It has been used successfully on MSYS. Some special properties about this b

Re: [Mingw-w64-public] multiple definition of _encode_pointer/_decode_pointer

2010-09-20 Thread Ozkan Sezer
On Mon, Sep 20, 2010 at 12:32 PM, Dongsheng Song wrote: > Hi all, > > When I compile cx_Oracle, I got the warn/error: > > O:\gcc-4.5-w32\bin\gcc.exe -mno-cygwin -shared -s > build\temp.win32-2.6-11g\Release\cx_oracle.o > build\temp.win32-2.6-11g\Release\cx_Oracle.def > -LC:\opt\oracle\product\11.2

[Mingw-w64-public] multiple definition of _encode_pointer/_decode_pointer

2010-09-20 Thread Dongsheng Song
Hi all, When I compile cx_Oracle, I got the warn/error: O:\gcc-4.5-w32\bin\gcc.exe -mno-cygwin -shared -s build\temp.win32-2.6-11g\Release\cx_oracle.o build\temp.win32-2.6-11g\Release\cx_Oracle.def -LC:\opt\oracle\product\11.2\master\bin -LC:\opt\oracle\product\11.2\master -LC:\opt\oracle\product