Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-09-14)

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 6:38 AM, NightStrike nightstr...@gmail.com wrote: On Sat, Sep 18, 2010 at 3:52 PM, Ozkan Sezer seze...@gmail.com wrote: On Sat, Sep 18, 2010 at 7:17 PM, Wolfgang Glas wolfgang.g...@ev-i.at wrote: On 2010-09-18 18:03, NightStrike wrote: On Sat, Sep 18, 2010 at 11:10 AM,

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

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 6:34 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 9:54 AM, JonY jo...@users.sourceforge.net wrote: All the headers provided under our include directory are already part of sdk, therefore I don't know how a separation can be possible. Admins?

[Mingw-w64-public] GCC and cloog-ppl linking to ppl giving undefined references to libstdc++ symbols

2010-09-19 Thread Ruben Van Boxem
Hi, When I try to build GCC with ppl/cloog-ppl for the Graphite optimization framework, bootstrap fails with undefined references in ppl_c.a to libstdc++ symbols (quite logical, because ppl is written in c++...). How can I solve this? Is it impossible to build bootstrap GCC with Graphite or is

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

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 1:11 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 4:54 PM, Ozkan Sezer seze...@gmail.com wrote: I said that assuming mingw-w64 was following MS. Ozkan where does usb.h live in MS's SDK stack? Dongsheng Song is correct that WDK has it in the api

Re: [Mingw-w64-public] GCC and cloog-ppl linking to ppl giving undefined references to libstdc++ symbols

2010-09-19 Thread JonY
On 9/19/2010 17:50, Ruben Van Boxem wrote: Hi, When I try to build GCC with ppl/cloog-ppl for the Graphite optimization framework, bootstrap fails with undefined references in ppl_c.a to libstdc++ symbols (quite logical, because ppl is written in c++...). How can I solve this? Is it

Re: [Mingw-w64-public] GCC and cloog-ppl linking to ppl giving undefined references to libstdc++ symbols

2010-09-19 Thread Ruben Van Boxem
2010/9/19 Ruben Van Boxem vanboxem.ru...@gmail.com 2010/9/19 JonY jo...@users.sourceforge.net On 9/19/2010 17:50, Ruben Van Boxem wrote: Hi, When I try to build GCC with ppl/cloog-ppl for the Graphite optimization framework, bootstrap fails with undefined references in ppl_c.a to

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

2010-09-19 Thread Xiaofan Chen
On Sun, Sep 19, 2010 at 6:18 PM, Ozkan Sezer seze...@gmail.com wrote: Yes WDK has several directories of headers. Apparently api sub-directory is more than the SDK counterpart since it includes many files not included in the SDK. The point is, the api subdirectory also contains windows.h,

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

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 1:40 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 6:18 PM, Ozkan Sezer seze...@gmail.com wrote: Yes WDK has several directories of headers. Apparently api sub-directory is more than the SDK counterpart since it includes many files not included in

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

2010-09-19 Thread Xiaofan Chen
On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer seze...@gmail.com 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 other software that expect usb.h out of ddk subdirectory, then? Please name

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

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 2:03 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer seze...@gmail.com 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 other

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

2010-09-19 Thread Cesar Strauss
On 17/9/2010 12:58, 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. You are welcome to join the MSYS team on mingw.org. You may use the MSYS mailing list, if you wish, to help coordinate this effort.

[Mingw-w64-public] GCC 4.6-20100911 error due to -Werror

2010-09-19 Thread Ruben Van Boxem
Hi, With GCC 4.6 snapshot dated 20100911, I have this error: /home/Ruben/mingw64/build64/gcc/./prev-gcc/xgcc -B/home/Ruben/mingw64/build64/gcc/./prev-gcc/ -B/mingw64/x86_64-w64-mingw32/bin/ -L/mingw64/x86_64-w64-mingw32/lib -L/mingw64/mingw/lib -isystem /mingw64/x86_64-w64-mingw32/include

Re: [Mingw-w64-public] GCC 4.6-20100911 error due to -Werror

2010-09-19 Thread Ruben Van Boxem
2010/9/19 Ozkan Sezer seze...@gmail.com http://gcc.gnu.org/ml/gcc-patches/2009-08/msg01669.html -- Ozkan Wow, a full year passed without a fix :S... Thanks for the link. Ruben -- Start uncovering the many

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

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

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

2010-09-19 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 8:28 PM, Kai Tietz ktiet...@googlemail.com wrote: 2010/9/19 Ozkan Sezer seze...@gmail.com: On Sun, Sep 19, 2010 at 2:03 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 6:44 PM, Ozkan Sezer seze...@gmail.com wrote: However, MinGW does not break

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

2010-09-19 Thread Xiaofan Chen
On Mon, Sep 20, 2010 at 1:28 AM, Kai Tietz ktiet...@googlemail.com wrote: The usb.h header is here in our platform headers as we need it for the case that no ddk is installed and somebody wants to use winusb.h header. OK this is a very good reason. WinUSB is useful. And indeed using WinUSB