[Mingw-w64-public] GCC problem with *.la files in sysroot/lib64

2010-09-18 Thread Ruben Van Boxem
Hi, I have built a toolchain using attached script, and while using my in-progress fancy build script, I noticed that while compiling ppl, the *.la files in lib64 contained the following: # Directory that this library needs to be installed in:

Re: [Mingw-w64-public] GCC problem with *.la files in sysroot/lib64

2010-09-18 Thread Teemu Nätkinniemi
I have built a toolchain using attached script, and while using my in-progress fancy build script, I noticed that while compiling ppl, the *.la files in lib64 contained the following: # Directory that this library needs to be installed in:

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

2010-09-18 Thread Ozkan Sezer
On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer seze...@gmail.com wrote: 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

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

2010-09-18 Thread NightStrike
On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer seze...@gmail.com wrote: On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer seze...@gmail.com wrote: 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

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

2010-09-18 Thread Wolfgang Glas
On 2010-09-18 18:03, NightStrike wrote: On Sat, Sep 18, 2010 at 11:10 AM, Ozkan Sezer seze...@gmail.com wrote: On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer seze...@gmail.com wrote: [snip] There is an optional small package in them, pr45300.zip, which is an update for the C++ headers cstdio,

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

2010-09-18 Thread Ozkan Sezer
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, Ozkan Sezer seze...@gmail.com wrote: On Wed, Sep 15, 2010 at 9:49 AM, Ozkan Sezer seze...@gmail.com wrote: [snip] There is an optional small

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

2010-09-18 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 12, 2010 at 5:34 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Thu, Sep 9, 2010 at 3:53 AM, Ozkan Sezer seze...@gmail.com wrote: 2. the name of your src/usb.h is, well, usb.h, and it conflicts, ie. searched

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

2010-09-18 Thread Xiaofan Chen
On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer seze...@gmail.com wrote: On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen xiaof...@gmail.com wrote: I think the MinGW-w64 newly included usb.h will break many existing software which uses libusb-win32. For example, libftdi's header is called ftdi.h

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

2010-09-18 Thread Ozkan Sezer
On Sun, Sep 19, 2010 at 2:56 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezer seze...@gmail.com wrote: On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chen xiaof...@gmail.com wrote: I think the MinGW-w64 newly included usb.h will break many existing software

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

2010-09-18 Thread JonY
On 9/19/2010 08:00, Ozkan Sezer wrote: On Sun, Sep 19, 2010 at 2:56 AM, Xiaofan Chenxiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 7:50 AM, Ozkan Sezerseze...@gmail.com wrote: On Sun, Sep 19, 2010 at 2:38 AM, Xiaofan Chenxiaof...@gmail.com wrote: I think the MinGW-w64 newly included

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

2010-09-18 Thread Xiaofan Chen
On Sun, Sep 19, 2010 at 9:03 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? Personally, I think deviating from MS is a bad idea. If ms puts it in the

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

2010-09-18 Thread Xiaofan Chen
On Sun, Sep 19, 2010 at 9:44 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Sun, Sep 19, 2010 at 9:03 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?

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

2010-09-18 Thread Dongsheng Song
On Sun, Sep 19, 2010 at 07:50, Ozkan Sezer seze...@gmail.com wrote: AFAIK, usb.h is out of ddk because it is part of ms platform sdk, therefore, it _needs_ to be out of a ddk subdirectory for proper compatibility. No, usb.h is in MS WDK 7.1 now: C:\opt\WinDDK\7.1\inc\apidir *usb* 驱动器 C

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

2010-09-18 Thread NightStrike
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, Ozkan Sezer seze...@gmail.com wrote: On Wed, Sep 15, 2010 at 9:49 AM,