Re: [Mingw-w64-public] Sezeros gdb builds - python support

[Jarrod Chesney <jarrod.chesney@gm...>]

On 01/05/2010, at 6:16 AM, Ozkan Sezer wrote:

> On Fri, Apr 30, 2010 at 11:12 PM, NightStrike <nightstrike@...> wrote:
>> On Mon, Feb 15, 2010 at 9:57 PM, Jarrod Chesney
>> <jarrod.chesney@...> wrote:
>>> Hi All
>>>        When using the gdb provided with sezeros mingw builds gdb does not seem to support python.
>>> I would like it to so that i can "pretty print" stl containers.
>>> 
>>> I tested it like this
>>> run gdb
>>> execute the three lines
>>> 
>>> python
>>> print "hello"
>>> end
>>> 
>>> Python scripting is not supported in this copy of GDB.
>>> 
>>> It would be great if this was supported.
>> 
>> Is this still the case?  If so, we have a guy here that builds gdb for us.
> 
> Well, it should still be, because I still don't build gdb with python support ;)
> (Python may be a pain to gather its all dependencies, so I leave it out it my
> toolchain builds.)

gdb needs python support so that it can support pretty print for stl containers (at the very least)
this should require only the python builtins. The problem here is that it needs to be statically linked into gdb and python doesn't compile for mingw-w64 at this stage.

Re: [Mingw-w64-public] Sezeros gdb builds - python support

[Ozkan Sezer <sezeroz@gm...>]

On Fri, Apr 30, 2010 at 11:12 PM, NightStrike <nightstrike@...> wrote:
> On Mon, Feb 15, 2010 at 9:57 PM, Jarrod Chesney
> <jarrod.chesney@...> wrote:
>> Hi All
>>        When using the gdb provided with sezeros mingw builds gdb does not seem to support python.
>> I would like it to so that i can "pretty print" stl containers.
>>
>> I tested it like this
>> run gdb
>> execute the three lines
>>
>> python
>> print "hello"
>> end
>>
>> Python scripting is not supported in this copy of GDB.
>>
>> It would be great if this was supported.
>
> Is this still the case?  If so, we have a guy here that builds gdb for us.

Well, it should still be, because I still don't build gdb with python support ;)
(Python may be a pain to gather its all dependencies, so I leave it out it my
toolchain builds.)

Re: [Mingw-w64-public] problem with mingw and vista 64 compiling

[NightStrike <nightstrike@gm...>]

On Sun, Feb 14, 2010 at 3:54 PM, bluetxxth <bluetxxth@...> wrote:
> Hi there,
>
>
>
> I have used eclipse to program in java, however I have recently installed
> the eclipse cdt in order to program in c. When I install all the components
> I think I need that is
>
>
>
> windows vista x64 ultimate
> eclipse-SDK-3.5.1-win32
> mingw-w32-bin_i686-mingw_20100123_sezero
> MSYS-1.0.11
>
>
>
> I make a simple hello world program in which I use a simple printf and the
> program compiles no problem. However if I add a scanf then I get a weird
> output and I think that it has to do with something malfunctioning in
> eclipse.
>
>
>
> # include <stdio.h>
>
> # include <stdlib.h>
>
>
>
> int main (void){
>
>
>
> char name [10];
>
>
>
> printf("enter name: ");
>
> scanf("%s", name);
>
>
>
> printf("the name is %s",name);
>
>
>
> return 0;
>
> }
>
>
>
> when trying to build this I get the following message:
>
>
>
>
>
> **** Build of configuration Debug for project print ****
>
>
>
> **** Internal Builder is used for build               ****
>
> Nothing to build for print
>
>
>
>
>
> In addition to this the result of the above in the eclipse console  is as
> follows...:
>
>
>
> Enter your name: the name is
>
>
>
>
>
> ...which is totally wrong!
>
>
>
> Is there anyone who can help me set it up correctly???

Still having issues?

Re: [Mingw-w64-public] Sezeros gdb builds - python support

[NightStrike <nightstrike@gm...>]

On Mon, Feb 15, 2010 at 9:57 PM, Jarrod Chesney
<jarrod.chesney@...> wrote:
> Hi All
>        When using the gdb provided with sezeros mingw builds gdb does not seem to support python.
> I would like it to so that i can "pretty print" stl containers.
>
> I tested it like this
> run gdb
> execute the three lines
>
> python
> print "hello"
> end
>
> Python scripting is not supported in this copy of GDB.
>
> It would be great if this was supported.

Is this still the case?  If so, we have a guy here that builds gdb for us.

Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.4 (2010-04-28)

[NightStrike <nightstrike@gm...>]

On Thu, Apr 29, 2010 at 6:52 AM, Ozkan Sezer <sezeroz@...> wrote:
> On Thu, Apr 29, 2010 at 1:49 PM, John Marriott
> <basilisk@...> wrote:
>> Hi Ozkan,
>>
>> Thanks for the update.
>>
>> A question if I may: do you have any plans for moving to the gcc 4.5
>> release?
>>
>
> Probably, although I think it would be best to wait for 4.5.1 release
> to have the 4.5-series fairly stabilized.  (Don't know when it will be
> out, though, around june? july?)

July

Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.4 (2010-04-28)

[Ozkan Sezer <sezeroz@gm...>]

On Thu, Apr 29, 2010 at 1:49 PM, John Marriott
<basilisk@...> wrote:
> Hi Ozkan,
>
> Thanks for the update.
>
> A question if I may: do you have any plans for moving to the gcc 4.5
> release?
>

Probably, although I think it would be best to wait for 4.5.1 release
to have the 4.5-series fairly stabilized.  (Don't know when it will be
out, though, around june? july?)

--
Ozkan


> On 29-Apr-2010 20:24, Ozkan Sezer wrote:
>>
>> 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 targetting Win32 ->  Personal Builds  and
>> -  Toolchains targetting Win64 ->  Personal Builds
>>
>> Changes since the previous 2010-04-10/2010-04-27 build:
>> - The mingw-w64 crt and headers updated to r2266 which contains an x64
>>   compatibility fix among other things.
>> - Gcc updated to the 4.4.4 prerelease version, svn rev. 158621. (After
>>   just about an hour I uploaded the files, the same gcc snapshot was
>>   marked as 4.4.4-release at rev. 158895 ;)
>> - All other software has been updated to the latest available versions
>>   as of 2010-04-28, 17:10 GMT.
>>
>> - Compatibility Notice:  ** No leading underscore **
>> ------------------------------------------------------------------------
>> Unlike the other builds from mingw-w64 up to 2010-04-27, these new win64
>> targetting toolchains do *not* prepend an undersocore to the symbols and
>> follows the MSVC x64 convention.  Therefore, any of the link libraries
>> from previous toolchains are incompatible with the ones created by these
>> new builds.
>>
>> - Note: the<install_dir>/include path "problem" of the native builds is
>>   not looked into, yet. Maybe in the future builds.
>>
>>
>> Versions:
>> ---------
>>
>> Common in both cross- and native-toolchains:
>>
>> gcc : svn rev. 158621 (4.4.4 prerelease with many patches)
>> binutils : 2.20.51 (cvs, 2010-04-28 17:10 GMT)
>> mingw-w64-crt : svn revision 2263 (2010-04-21)
>> mingw-w64-headers : svn revision 2266 (2010-04-28), with a
>>  couple of patches.
>> glext headers: 2010-03-17 (from the Khronos Group)
>> pthreads-win32: 2.9.0 (cvs, 2010-02-28 20:00 GMT)
>>  with w64 patch applied.
>>
>> In native-toolchains only:
>>
>> gmp : 4.3.2 (with w64 patch applied)
>> mpfr: 2.4.2-p3
>> mpc : 0.8.1
>> gdb : 7.1.50 (cvs, 2010-04-28 17:10 GMT, with
>>  minor w64 patches applied.)
>> make: 3.81.90 (cvs, 2010-02-02 15:20 GMT, with
>>  w64 patches applied according to savannah bug
>>  items 27809 and 27825, and patched further to
>>  kill a horde of compiler warnings)
>> gendef, libmangle: from mingw-w64 svn/trunk
>>
>>
>> File names:
>> -----------
>>
>> * Source:
>>
>> - mingw-w64-src_20100428_sezero.tar.gz
>>
>>
>> * Targetting Win64:
>>
>> - mingw-w64-bin_x86_64-mingw_20100428_sezero.zip
>>   native compiler toolchain for running on x64-windows
>>   host and creating x64-windows binaries.
>>
>> - mingw-w64-bin_i686-mingw_20100428_sezero.zip
>>   cross compiler toolchain for running on x86-windows
>>   host but creating x64-windows binaries.
>>
>> - mingw-w64-bin_i686-linux_20100428_sezero.tar.gz
>>   cross compiler toolchain for running on a i686-linux
>>   host and creating x64-windows binaries.
>>
>> - mingw-w64-bin_x86_64-linux_20100428_sezero.tar.gz
>>   cross compiler toolchain for running on a x86_64-linux
>>   host and creating x64-windows binaries.
>>
>>
>> * Targetting Win32:
>>
>> - mingw-w32-bin_i686-mingw_20100428_sezero.zip
>>   native compiler toolchain for running on x86-windows
>>   host and creating x86-windows binaries.
>>
>> - mingw-w32-bin_i686-linux_20100428_sezero.tar.gz
>>   cross compiler toolchain for running on a i686-linux
>>   host and creating x86-windows binaries.
>>
>> - mingw-w32-bin_x86_64-linux_20100428_sezero.tar.gz
>>   cross compiler toolchain for running on a x86_64-linux
>>   host and creating x86-windows binaries.
>>
>> --
>> Ozkan
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mingw-w64-public mailing list
>> Mingw-w64-public@...
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>

Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.4 (2010-04-28)

[John Marriott <basilisk@in...>]

Hi Ozkan,

Thanks for the update.

A question if I may: do you have any plans for moving to the gcc 4.5 
release?

On 29-Apr-2010 20:24, Ozkan Sezer wrote:
> 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 targetting Win32 ->  Personal Builds  and
> -  Toolchains targetting Win64 ->  Personal Builds
>
> Changes since the previous 2010-04-10/2010-04-27 build:
> - The mingw-w64 crt and headers updated to r2266 which contains an x64
>    compatibility fix among other things.
> - Gcc updated to the 4.4.4 prerelease version, svn rev. 158621. (After
>    just about an hour I uploaded the files, the same gcc snapshot was
>    marked as 4.4.4-release at rev. 158895 ;)
> - All other software has been updated to the latest available versions
>    as of 2010-04-28, 17:10 GMT.
>
> - Compatibility Notice:  ** No leading underscore **
> ------------------------------------------------------------------------
> Unlike the other builds from mingw-w64 up to 2010-04-27, these new win64
> targetting toolchains do *not* prepend an undersocore to the symbols and
> follows the MSVC x64 convention.  Therefore, any of the link libraries
> from previous toolchains are incompatible with the ones created by these
> new builds.
>
> - Note: the<install_dir>/include path "problem" of the native builds is
>    not looked into, yet. Maybe in the future builds.
>
>
> Versions:
> ---------
>
> Common in both cross- and native-toolchains:
>
> gcc : svn rev. 158621 (4.4.4 prerelease with many patches)
> binutils : 2.20.51 (cvs, 2010-04-28 17:10 GMT)
> mingw-w64-crt : svn revision 2263 (2010-04-21)
> mingw-w64-headers : svn revision 2266 (2010-04-28), with a
>   couple of patches.
> glext headers: 2010-03-17 (from the Khronos Group)
> pthreads-win32: 2.9.0 (cvs, 2010-02-28 20:00 GMT)
>   with w64 patch applied.
>
> In native-toolchains only:
>
> gmp : 4.3.2 (with w64 patch applied)
> mpfr: 2.4.2-p3
> mpc : 0.8.1
> gdb : 7.1.50 (cvs, 2010-04-28 17:10 GMT, with
>   minor w64 patches applied.)
> make: 3.81.90 (cvs, 2010-02-02 15:20 GMT, with
>   w64 patches applied according to savannah bug
>   items 27809 and 27825, and patched further to
>   kill a horde of compiler warnings)
> gendef, libmangle: from mingw-w64 svn/trunk
>
>
> File names:
> -----------
>
> * Source:
>
> - mingw-w64-src_20100428_sezero.tar.gz
>
>
> * Targetting Win64:
>
> - mingw-w64-bin_x86_64-mingw_20100428_sezero.zip
>    native compiler toolchain for running on x64-windows
>    host and creating x64-windows binaries.
>
> - mingw-w64-bin_i686-mingw_20100428_sezero.zip
>    cross compiler toolchain for running on x86-windows
>    host but creating x64-windows binaries.
>
> - mingw-w64-bin_i686-linux_20100428_sezero.tar.gz
>    cross compiler toolchain for running on a i686-linux
>    host and creating x64-windows binaries.
>
> - mingw-w64-bin_x86_64-linux_20100428_sezero.tar.gz
>    cross compiler toolchain for running on a x86_64-linux
>    host and creating x64-windows binaries.
>
>
> * Targetting Win32:
>
> - mingw-w32-bin_i686-mingw_20100428_sezero.zip
>    native compiler toolchain for running on x86-windows
>    host and creating x86-windows binaries.
>
> - mingw-w32-bin_i686-linux_20100428_sezero.tar.gz
>    cross compiler toolchain for running on a i686-linux
>    host and creating x86-windows binaries.
>
> - mingw-w32-bin_x86_64-linux_20100428_sezero.tar.gz
>    cross compiler toolchain for running on a x86_64-linux
>    host and creating x86-windows binaries.
>
> --
> Ozkan
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@...
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

[Mingw-w64-public] Custom toolchain build with gcc-4.4.4 (2010-04-28)

[Ozkan Sezer <sezeroz@gm...>]

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 targetting Win32 -> Personal Builds  and
-  Toolchains targetting Win64 -> Personal Builds

Changes since the previous 2010-04-10/2010-04-27 build:
- The mingw-w64 crt and headers updated to r2266 which contains an x64
  compatibility fix among other things.
- Gcc updated to the 4.4.4 prerelease version, svn rev. 158621. (After
  just about an hour I uploaded the files, the same gcc snapshot was
  marked as 4.4.4-release at rev. 158895 ;)
- All other software has been updated to the latest available versions
  as of 2010-04-28, 17:10 GMT.

- Compatibility Notice:  ** No leading underscore **
------------------------------------------------------------------------
Unlike the other builds from mingw-w64 up to 2010-04-27, these new win64
targetting toolchains do *not* prepend an undersocore to the symbols and
follows the MSVC x64 convention.  Therefore, any of the link libraries
from previous toolchains are incompatible with the ones created by these
new builds.

- Note: the <install_dir>/include path "problem" of the native builds is
  not looked into, yet. Maybe in the future builds.


Versions:
---------

Common in both cross- and native-toolchains:

gcc : svn rev. 158621 (4.4.4 prerelease with many patches)
binutils : 2.20.51 (cvs, 2010-04-28 17:10 GMT)
mingw-w64-crt : svn revision 2263 (2010-04-21)
mingw-w64-headers : svn revision 2266 (2010-04-28), with a
 couple of patches.
glext headers: 2010-03-17 (from the Khronos Group)
pthreads-win32: 2.9.0 (cvs, 2010-02-28 20:00 GMT)
 with w64 patch applied.

In native-toolchains only:

gmp : 4.3.2 (with w64 patch applied)
mpfr: 2.4.2-p3
mpc : 0.8.1
gdb : 7.1.50 (cvs, 2010-04-28 17:10 GMT, with
 minor w64 patches applied.)
make: 3.81.90 (cvs, 2010-02-02 15:20 GMT, with
 w64 patches applied according to savannah bug
 items 27809 and 27825, and patched further to
 kill a horde of compiler warnings)
gendef, libmangle: from mingw-w64 svn/trunk


File names:
-----------

* Source:

- mingw-w64-src_20100428_sezero.tar.gz


* Targetting Win64:

- mingw-w64-bin_x86_64-mingw_20100428_sezero.zip
  native compiler toolchain for running on x64-windows
  host and creating x64-windows binaries.

- mingw-w64-bin_i686-mingw_20100428_sezero.zip
  cross compiler toolchain for running on x86-windows
  host but creating x64-windows binaries.

- mingw-w64-bin_i686-linux_20100428_sezero.tar.gz
  cross compiler toolchain for running on a i686-linux
  host and creating x64-windows binaries.

- mingw-w64-bin_x86_64-linux_20100428_sezero.tar.gz
  cross compiler toolchain for running on a x86_64-linux
  host and creating x64-windows binaries.


* Targetting Win32:

- mingw-w32-bin_i686-mingw_20100428_sezero.zip
  native compiler toolchain for running on x86-windows
  host and creating x86-windows binaries.

- mingw-w32-bin_i686-linux_20100428_sezero.tar.gz
  cross compiler toolchain for running on a i686-linux
  host and creating x86-windows binaries.

- mingw-w32-bin_x86_64-linux_20100428_sezero.tar.gz
  cross compiler toolchain for running on a x86_64-linux
  host and creating x86-windows binaries.

--
Ozkan

Re: [Mingw-w64-public] Cross-compiling mingw64

[NightStrike <nightstrike@gm...>]

The easiest way is to download our makefile from svn at
experimental/buildsystem/makebuildroot.mk and use that.  You can set
the target arch variable to determine if your resultant toolchain will
target win32 or win64.  I would highly recommend using two separate
toolchains and not trying to build a single multilib toolchain.

On Wed, Apr 28, 2010 at 5:40 PM, Simson Garfinkel <simsong@...> wrote:
> Hi. I am looking for simple instructions that tell me how to compile mingw64 on a Mac to output 32-bit and 64-bit windows executables.  I thought that this would be straightforward, but I just can't find the documentation in either the downloads or the website. I know it is possible to do this because I have mingw32 operating from the MacPorts collection. But i can't figure out how to do mingw64.
>
> Thanks!
> ------------------------------------------------------------------------------
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@...
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

[Mingw-w64-public] Cross-compiling mingw64

[Simson Garfinkel <simsong@ac...>]

Hi. I am looking for simple instructions that tell me how to compile mingw64 on a Mac to output 32-bit and 64-bit windows executables.  I thought that this would be straightforward, but I just can't find the documentation in either the downloads or the website. I know it is possible to do this because I have mingw32 operating from the MacPorts collection. But i can't figure out how to do mingw64. 

Thanks!

Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable not honoured.

[NightStrike <nightstrike@gm...>]

On Thu, Apr 22, 2010 at 5:33 AM, Sisyphus <sisyphus1@...> wrote:
>
> ----- Original Message ----- From: "NightStrike" <nightstrike@...>
> To: "Doug Semler" <dougsemler@...>
>
>>> LIBRARY_PATH is ignored in cross compilers.
>
>>
>> The toolchain in question is host=win32 target=win64.  So it is meant
>> to cross compile from a 32-bit windows generating binaries for a
>> 64-bit windows.  It just so happens that you can run this on win64,
>> since win64 can run win32 programs.  But that doesn't mean that we
>> should treat it like it's not a cross compiler.
>>
>
> Ok - I think I get the picture.
>
> If I want ot make use of the LIBRARY_PATH environment variable I should grab
> sezero's binary (which is not a cross-compiler) and use it instead. I've
> just checked, and sezero's build does honour the LIBRARY_PATH setting.

Yup!

> Thanks Doug, NightStrike.

Np

Re: [Mingw-w64-public] wxWidgets

[kmx <kmx@vo...>]

Dne 27.4.2010 2:20, Jarrod Chesney napsal(a):
> Hi Mingw-w64'ers
> 	Does anyone have an existing patch set or porting efforts wit wxWidgets compiled with mingw-w64 32/64bit?
> Otherwise, Does anyone know how i can get in contact with  zhou drangon who has precompiled binaries for it.
>
> I want to build wxWidgets from source and i also will setup a few build slaves for wxWidgets with mingw-w64.
>   

Hi,

I have just some info from Alien::wxWidgets perl module maintainers that
it is now possible to build wxWidgets-2.8.11 with mingw-w64 compiler
(both 32-bit/64-bit) with a little patching.

Please have a look at:
https://wxperl.svn.sourceforge.net/svnroot/wxperl/Alien-wxWidgets/trunk/patches/

The relevant patches for 2.8.11 are IMHO:
wxMSW-2.8.0-setup_u.patch
wxMSW-2.8.10-config.patch
wxMSW-2.8.11-makefiles.patch
wxMSW-2.8.10-w64-mslu.patch
wxMSW-2.8.10-w64-winhash.patch
wxMSW-2.8.11-w64.patch
wxMSW-2.8.10-w64-stc.patch
wxMSW-2.8.11-filefn.patch
wxWidgets-2.8.0-magic.patch
(do not be nervous that some of them are named ...2.8.10...)

--
kmx

Re: [Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Mario Emmenlauer <mario@em...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi Doug,

On 04/26/2010 03:37 PM, Doug Semler wrote:
> On Mon, Apr 26, 2010 at 6:25 AM, Mario Emmenlauer <mario@...> wrote:
>>> On 04/25/2010 04:48 PM, Kai Tietz wrote:
>>>> 2010/4/25 Mario Emmenlauer <mario@...>:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I fail to build a canadian cross with mingw Revision: 2263 (current
>>>>> trunk).
>>>>>
>>>>> The error happens during "make all-target-libgcc", message is:
>>>>>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>>>>>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>>>>>
>>>>> There are more identical errors for other libs like kernel32 and
>>>>> msvcrt.
>>>>>
>>>>>
>>>>> objdump lists the correct format:
>>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>>>>>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>>>>>    [...]
>>>>>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>>>>>
>>>>> Also, ld seems to be valid:
>>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>>>>>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big
>>>>>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>>>>>
>>>>>
>>>>> Here is what I tried:
>>>>>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>>>>>  - makefile: experimental/buildsystem/makebuildroot.mk
>>>>>  - compile instructions from mingw64 sourceforge wiki
>>>>>
>>>>> Compiled with various combinations of
>>>>>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>>>>>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>>>>>
>>>>> Operating system:
>>>>>  - Ubuntu 9.10 x86_64
>>>>>  - Debian testing x86_64
>>>>>  - Ubuntu 8.10 x86_64
>>>>>
>>>>> All result in the identical error message about 'skipping incompatible'
>>>>> when searching for mingw libs.
>>>>
>>>> Well, for me it is looking like that either your binutils version
>>>> isn't a x64 defaulted one, or the libraries are build for 32-bit and
>>>> not for 64-bit. Did you used for crt build '--enable-lib32' or
>>>> '--enable-lib64'?
>>>
>>> Sorry that I forgot that crucial piece of information!
>>>
>>> I tried both with and without multilib, same result. Based on a
>>> suggestion from jon_y in IRC, I concentrate on without multilib first.
>>> For leaving out multilib, I do not add any of '--enable-lib32' or
>>> '--enable-lib64' to configure of mingw crt (but leave the default).
>>> For gcc and binutils, I do add '--disable-multilib' to configure.
>>>
>>> Is there an easy test whether any of the components targets the wrong
>>> architecture?
>>
>> I just checked from an i686 Ubuntu Hardy, same error. So its not related
>> to the x86_64 architecture of the host OS.
>>
>> Can anybody successfully compile a canadian cross from Linux with
>> current trunk? If yes, what are the specs and compile instructions
>> used, so I have a reference?
>>
>> Cheers,
>>
> 
> Not with the current trunk but I've managed to get the 4.5 build going.
> 
> I have a few patches that "fix" the gcc build system and also use
> version-specific-libraries.  Which means, unfortunately, my build
> scripts wouldn't work too well for you without the patches.
> 
> If you want, I can send them but you'll have to apply some patches to
> make it work right for you :-/

Great, thats very good news! Your setup would absolutely be an option
for me! Since I don't require mingw in a production environment, I'm
very flexible with the versions and everything. Also I don't require
multilib, so I'm all flexible :-)

Could you please send me the patches, and your specific version they
apply to? I'll test them right away :-)

Cheers,

   Mario

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvWeCsACgkQPb/HY94yy8S8ZwCgi5myiEIqqnqIk1gyAgX12PCl
kBcAn1u0mfNS4Vam0ZN3hFF7HpVIK5m1
=RQgk
-----END PGP SIGNATURE-----

Re: [Mingw-w64-public] wxWidgets

[Tony Theodore <tonyt@lo...>]

On 27 April 2010 10:20, Jarrod Chesney <jarrod.chesney@...> wrote:
> Hi Mingw-w64'ers
>        Does anyone have an existing patch set or porting efforts wit wxWidgets compiled with mingw-w64 32/64bit?
> Otherwise, Does anyone know how i can get in contact with  zhou drangon who has precompiled binaries for it.
>
> I want to build wxWidgets from source and i also will setup a few build slaves for wxWidgets with mingw-w64.

The build scripts are here:

http://code.google.com/p/mingw-w64-dgn/source/checkout

though I couldn't get them to work in a small amount of time.

Cheers,

Tony

[Mingw-w64-public] wxWidgets

[Jarrod Chesney <jarrod.chesney@gm...>]

Hi Mingw-w64'ers
	Does anyone have an existing patch set or porting efforts wit wxWidgets compiled with mingw-w64 32/64bit?
Otherwise, Does anyone know how i can get in contact with  zhou drangon who has precompiled binaries for it.

I want to build wxWidgets from source and i also will setup a few build slaves for wxWidgets with mingw-w64.

Regards 256fx

Re: [Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Doug Semler <dougsemler@gm...>]

On Mon, Apr 26, 2010 at 6:25 AM, Mario Emmenlauer <mario@...> wrote:
>> Hi Kai,
>>
>> On 04/25/2010 04:48 PM, Kai Tietz wrote:
>>> 2010/4/25 Mario Emmenlauer <mario@...>:
>>>>
>>>> Hi all,
>>>>
>>>> I fail to build a canadian cross with mingw Revision: 2263 (current
>>>> trunk).
>>>>
>>>> The error happens during "make all-target-libgcc", message is:
>>>>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>>>>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>>>>
>>>> There are more identical errors for other libs like kernel32 and
>>>> msvcrt.
>>>>
>>>>
>>>> objdump lists the correct format:
>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>>>>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>>>>    [...]
>>>>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>>>>
>>>> Also, ld seems to be valid:
>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>>>>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big
>>>> \
>>>>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>>>>
>>>>
>>>> Here is what I tried:
>>>>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>>>>  - makefile: experimental/buildsystem/makebuildroot.mk
>>>>  - compile instructions from mingw64 sourceforge wiki
>>>>
>>>> Compiled with various combinations of
>>>>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>>>>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>>>>
>>>> Operating system:
>>>>  - Ubuntu 9.10 x86_64
>>>>  - Debian testing x86_64
>>>>  - Ubuntu 8.10 x86_64
>>>>
>>>> All result in the identical error message about 'skipping incompatible'
>>>> when searching for mingw libs.
>>>
>>> Well, for me it is looking like that either your binutils version
>>> isn't a x64 defaulted one, or the libraries are build for 32-bit and
>>> not for 64-bit. Did you used for crt build '--enable-lib32' or
>>> '--enable-lib64'?
>>
>> Sorry that I forgot that crucial piece of information!
>>
>> I tried both with and without multilib, same result. Based on a
>> suggestion from jon_y in IRC, I concentrate on without multilib first.
>> For leaving out multilib, I do not add any of '--enable-lib32' or
>> '--enable-lib64' to configure of mingw crt (but leave the default).
>> For gcc and binutils, I do add '--disable-multilib' to configure.
>>
>> Is there an easy test whether any of the components targets the wrong
>> architecture?
>
> I just checked from an i686 Ubuntu Hardy, same error. So its not related
> to the x86_64 architecture of the host OS.
>
> Can anybody successfully compile a canadian cross from Linux with
> current trunk? If yes, what are the specs and compile instructions
> used, so I have a reference?
>
> Cheers,
>


On Mon, Apr 26, 2010 at 6:25 AM, Mario Emmenlauer <mario@...> wrote:
>> Hi Kai,
>>
>> On 04/25/2010 04:48 PM, Kai Tietz wrote:
>>> 2010/4/25 Mario Emmenlauer <mario@...>:
>>>>
>>>> Hi all,
>>>>
>>>> I fail to build a canadian cross with mingw Revision: 2263 (current
>>>> trunk).
>>>>
>>>> The error happens during "make all-target-libgcc", message is:
>>>>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>>>>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>>>>
>>>> There are more identical errors for other libs like kernel32 and
>>>> msvcrt.
>>>>
>>>>
>>>> objdump lists the correct format:
>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>>>>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>>>>    [...]
>>>>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>>>>
>>>> Also, ld seems to be valid:
>>>>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>>>>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big
>>>> \
>>>>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>>>>
>>>>
>>>> Here is what I tried:
>>>>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>>>>  - makefile: experimental/buildsystem/makebuildroot.mk
>>>>  - compile instructions from mingw64 sourceforge wiki
>>>>
>>>> Compiled with various combinations of
>>>>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>>>>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>>>>
>>>> Operating system:
>>>>  - Ubuntu 9.10 x86_64
>>>>  - Debian testing x86_64
>>>>  - Ubuntu 8.10 x86_64
>>>>
>>>> All result in the identical error message about 'skipping incompatible'
>>>> when searching for mingw libs.
>>>
>>> Well, for me it is looking like that either your binutils version
>>> isn't a x64 defaulted one, or the libraries are build for 32-bit and
>>> not for 64-bit. Did you used for crt build '--enable-lib32' or
>>> '--enable-lib64'?
>>
>> Sorry that I forgot that crucial piece of information!
>>
>> I tried both with and without multilib, same result. Based on a
>> suggestion from jon_y in IRC, I concentrate on without multilib first.
>> For leaving out multilib, I do not add any of '--enable-lib32' or
>> '--enable-lib64' to configure of mingw crt (but leave the default).
>> For gcc and binutils, I do add '--disable-multilib' to configure.
>>
>> Is there an easy test whether any of the components targets the wrong
>> architecture?
>
> I just checked from an i686 Ubuntu Hardy, same error. So its not related
> to the x86_64 architecture of the host OS.
>
> Can anybody successfully compile a canadian cross from Linux with
> current trunk? If yes, what are the specs and compile instructions
> used, so I have a reference?
>
> Cheers,
>
>   Mario
>

Not with the current trunk but I've managed to get the 4.5 build going.

I have a few patches that "fix" the gcc build system and also use
version-specific-libraries.  Which means, unfortunately, my build
scripts wouldn't work too well for you without the patches.

If you want, I can send them but you'll have to apply some patches to
make it work right for you :-/

Re: [Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Mario Emmenlauer <mario@em...>]

> Hi Kai,
>
> On 04/25/2010 04:48 PM, Kai Tietz wrote:
>> 2010/4/25 Mario Emmenlauer <mario@...>:
>>>
>>> Hi all,
>>>
>>> I fail to build a canadian cross with mingw Revision: 2263 (current
>>> trunk).
>>>
>>> The error happens during "make all-target-libgcc", message is:
>>>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>>>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>>>
>>> There are more identical errors for other libs like kernel32 and
>>> msvcrt.
>>>
>>>
>>> objdump lists the correct format:
>>>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>>>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>>>    [...]
>>>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>>>
>>> Also, ld seems to be valid:
>>>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>>>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big
>>> \
>>>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>>>
>>>
>>> Here is what I tried:
>>>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>>>  - makefile: experimental/buildsystem/makebuildroot.mk
>>>  - compile instructions from mingw64 sourceforge wiki
>>>
>>> Compiled with various combinations of
>>>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>>>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>>>
>>> Operating system:
>>>  - Ubuntu 9.10 x86_64
>>>  - Debian testing x86_64
>>>  - Ubuntu 8.10 x86_64
>>>
>>> All result in the identical error message about 'skipping incompatible'
>>> when searching for mingw libs.
>>
>> Well, for me it is looking like that either your binutils version
>> isn't a x64 defaulted one, or the libraries are build for 32-bit and
>> not for 64-bit. Did you used for crt build '--enable-lib32' or
>> '--enable-lib64'?
>
> Sorry that I forgot that crucial piece of information!
>
> I tried both with and without multilib, same result. Based on a
> suggestion from jon_y in IRC, I concentrate on without multilib first.
> For leaving out multilib, I do not add any of '--enable-lib32' or
> '--enable-lib64' to configure of mingw crt (but leave the default).
> For gcc and binutils, I do add '--disable-multilib' to configure.
>
> Is there an easy test whether any of the components targets the wrong
> architecture?

I just checked from an i686 Ubuntu Hardy, same error. So its not related
to the x86_64 architecture of the host OS.

Can anybody successfully compile a canadian cross from Linux with
current trunk? If yes, what are the specs and compile instructions
used, so I have a reference?

Cheers,

   Mario

Re: [Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Mario Emmenlauer <mario@em...>]

Hi Kai,

On 04/25/2010 04:48 PM, Kai Tietz wrote:
> 2010/4/25 Mario Emmenlauer <mario@...>:
>>
>> Hi all,
>>
>> I fail to build a canadian cross with mingw Revision: 2263 (current
>> trunk).
>>
>> The error happens during "make all-target-libgcc", message is:
>>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>>
>> There are more identical errors for other libs like kernel32 and msvcrt.
>>
>>
>> objdump lists the correct format:
>>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>>    [...]
>>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>>
>> Also, ld seems to be valid:
>>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big \
>>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>>
>>
>> Here is what I tried:
>>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>>  - makefile: experimental/buildsystem/makebuildroot.mk
>>  - compile instructions from mingw64 sourceforge wiki
>>
>> Compiled with various combinations of
>>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>>
>> Operating system:
>>  - Ubuntu 9.10 x86_64
>>  - Debian testing x86_64
>>  - Ubuntu 8.10 x86_64
>>
>> All result in the identical error message about 'skipping incompatible'
>> when searching for mingw libs.
> 
> Well, for me it is looking like that either your binutils version
> isn't a x64 defaulted one, or the libraries are build for 32-bit and
> not for 64-bit. Did you used for crt build '--enable-lib32' or
> '--enable-lib64'?

Sorry that I forgot that crucial piece of information!

I tried both with and without multilib, same result. Based on a
suggestion from jon_y in IRC, I concentrate on without multilib first.
For leaving out multilib, I do not add any of '--enable-lib32' or
'--enable-lib64' to configure of mingw crt (but leave the default).
For gcc and binutils, I do add '--disable-multilib' to configure.

Is there an easy test whether any of the components targets the wrong
architecture?

All the best,

   Mario

Re: [Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Kai Tietz <ktietz70@go...>]

2010/4/25 Mario Emmenlauer <mario@...>:
>
> Hi all,
>
> I fail to build a canadian cross with mingw Revision: 2263 (current
> trunk).
>
> The error happens during "make all-target-libgcc", message is:
>  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
>  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32
>
> There are more identical errors for other libs like kernel32 and msvcrt.
>
>
> objdump lists the correct format:
>  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
>  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
>    [...]
>    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64
>
> Also, ld seems to be valid:
>  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
>    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big \
>    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex
>
>
> Here is what I tried:
>  - makefile: experimental/buildsystem/makebuildroot-test.mk
>  - makefile: experimental/buildsystem/makebuildroot.mk
>  - compile instructions from mingw64 sourceforge wiki
>
> Compiled with various combinations of
>  - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
>  - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk
>
> Operating system:
>  - Ubuntu 9.10 x86_64
>  - Debian testing x86_64
>  - Ubuntu 8.10 x86_64
>
> All result in the identical error message about 'skipping incompatible'
> when searching for mingw libs.
>
>
> Thanks a lot for any help,
>
>   Mario
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@...
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

Well, for me it is looking like that either your binutils version
isn't a x64 defaulted one, or the libraries are build for 32-bit and
not for 64-bit. Did you used for crt build '--enable-lib32' or
'--enable-lib64'?

Regards,
Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

[Mingw-w64-public] ld: skipping incompatible build/root/mingw/lib/libmingw32.a

[Mario Emmenlauer <mario@em...>]

Hi all,

I fail to build a canadian cross with mingw Revision: 2263 (current
trunk).

The error happens during "make all-target-libgcc", message is:
  [cut]/build/root/x86_64-w64-mingw32/bin/ld: skipping incompatible \
  [cut]/build/root/mingw/lib/libmingw32.a when searching for -lmingw32

There are more identical errors for other libs like kernel32 and msvcrt.


objdump lists the correct format:
  [cut]/build/root/bin/x86_64-w64-mingw32-objdump --archive-headers \
  [cut]/build/root/x86_64-w64-mingw32/lib/libmingw32.a
    [...]
    lib64_libmingw32_a-tlsmcrt.o:     file format pe-x86-64

Also, ld seems to be valid:
  [cut]/build/root/bin/x86_64-w64-mingw32-ld: supported targets: \
    pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-little elf64-big \
    elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex


Here is what I tried:
 - makefile: experimental/buildsystem/makebuildroot-test.mk
 - makefile: experimental/buildsystem/makebuildroot.mk
 - compile instructions from mingw64 sourceforge wiki

Compiled with various combinations of
 - binutils-2.20.1, binutils-2.20.51 and binutils-trunk
 - gcc-4.4.3, gcc-4.5.0 and gcc-4.5.1-trunk

Operating system:
 - Ubuntu 9.10 x86_64
 - Debian testing x86_64
 - Ubuntu 8.10 x86_64

All result in the identical error message about 'skipping incompatible'
when searching for mingw libs.


Thanks a lot for any help,

   Mario

Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable not honoured.

[Sisyphus <sisyphus1@op...>]

----- Original Message ----- 
From: "NightStrike" <nightstrike@...>
To: "Doug Semler" <dougsemler@...>

>> LIBRARY_PATH is ignored in cross compilers.

>
> The toolchain in question is host=win32 target=win64.  So it is meant
> to cross compile from a 32-bit windows generating binaries for a
> 64-bit windows.  It just so happens that you can run this on win64,
> since win64 can run win32 programs.  But that doesn't mean that we
> should treat it like it's not a cross compiler.
>

Ok - I think I get the picture.

If I want ot make use of the LIBRARY_PATH environment variable I should grab 
sezero's binary (which is not a cross-compiler) and use it instead. I've 
just checked, and sezero's build does honour the LIBRARY_PATH setting.

Thanks Doug, NightStrike.

Cheers,
Rob 

Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable not honoured.

[Doug Semler <dougsemler@gm...>]

On Wed, Apr 21, 2010 at 3:30 PM, NightStrike <nightstrike@...> wrote:
> On Wed, Apr 21, 2010 at 11:41 AM, Doug Semler <dougsemler@...> wrote:
>> Well, it looks like the compiler may be being built with host !=
>> target... In other words it wasn't bootstrapped and has been
>> configured as a cross compiler...
>>
>> LIBRARY_PATH is ignored in cross compilers.
>
> That's because it is a cross compiler
>
>> The buildbot that builds this should probably override the
>> configuration guess, by both passing the --host=x86_64-w64-mingw32 on
>> the configure line, and also by passing --enable-bootstrap if it's
>> being built on a 64 windows machine.  I don't know how well this would
>> work, but it could be tried....
>>
>> If host != target, CROSS_DIRECTORY_STRUCTURE is defined, which then
>> turns off several environment variables (that wouldn't be suitable for
>> a cross compiler)...
>
> The toolchain in question is host=win32 target=win64.  So it is meant
> to cross compile from a 32-bit windows generating binaries for a
> 64-bit windows.  It just so happens that you can run this on win64,
> since win64 can run win32 programs.  But that doesn't mean that we
> should treat it like it's not a cross compiler.
>

You're right - sorry, I missed the part where he downloaded the i686
binaries...I assumed (standard disclaimer about assumptions here) that
he was using the x86_64 binaries

Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable not honoured.

[Роман Донченко <DXDragon@ya...>]

Sisyphus <sisyphus1@...> писал в своём  
письме Mon, 19 Apr 2010 04:06:11 +0500:

>
> Is there some other way of adding C:/_64/msys/1.0/local/lib to the  
> default
> library search path so that I can avoid using the -L switch all the time  
> ?
>

You can use spec file magic: http://www.mingw.org/wiki/SpecsFileHOWTO

Roman.

Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable not honoured.

[NightStrike <nightstrike@gm...>]

On Wed, Apr 21, 2010 at 11:41 AM, Doug Semler <dougsemler@...> wrote:
> Well, it looks like the compiler may be being built with host !=
> target... In other words it wasn't bootstrapped and has been
> configured as a cross compiler...
>
> LIBRARY_PATH is ignored in cross compilers.

That's because it is a cross compiler

> The buildbot that builds this should probably override the
> configuration guess, by both passing the --host=x86_64-w64-mingw32 on
> the configure line, and also by passing --enable-bootstrap if it's
> being built on a 64 windows machine.  I don't know how well this would
> work, but it could be tried....
>
> If host != target, CROSS_DIRECTORY_STRUCTURE is defined, which then
> turns off several environment variables (that wouldn't be suitable for
> a cross compiler)...

The toolchain in question is host=win32 target=win64.  So it is meant
to cross compile from a 32-bit windows generating binaries for a
64-bit windows.  It just so happens that you can run this on win64,
since win64 can run win32 programs.  But that doesn't mean that we
should treat it like it's not a cross compiler.

Re: [Mingw-w64-public] msvcr90 doesn't containing.

[Doug Semler <dougsemler@gm...>]

2010/4/21 Ozkan Sezer <sezeroz@...>:
> On Wed, Apr 21, 2010 at 11:38 AM, 罗勇刚(Yonggang Luo)
> <luoyonggang@...> wrote:
>> E:/CI/Tools//phoenix/mingw32/bin\gcc.exe -mno-cygwin -shared -s
>> build\temp.win32-2.6\Release\dulwich\_objects.o
>> build\temp.win32-2.6\Release\dulwich\_objects.def
>> -LE:\CI\tools\Python\libs -LE:\CI\tool
>> s\Python\PCbuild -lpython26 -lmsvcr90 -o
>> build\lib.win32-2.6\dulwich\_objects.pyd
>> e:/ci/tools/phoenix/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.5.0/../../../../i686-w64-mingw32/bin/ld.exe:
>> cannot find -lmsvcr90
>> collect2: ld returned 1 exit status
>> error: command 'gcc' failed with exit status 1
>>
>>
>> Once I using python setuptools build dulwich with
>> http://code.google.com/p/mingw-w64-dgn/
>> 32bit version gcc compiler.
>> But it's report that error. So did mingw-w64 accompany with msvcr90 or
>> dgn-mingw-w64 lost it?
>
> At present, mingw-w64 doesn't have a libmsvcr90.a
> link library. If you need/want that feature, please open an
> entry in our "Feature requests" tracker.
>

(Which, by the way, would require support for manifesting as well,
which is not going to be a small feat....)