On 9/15/2010 19:13, Wolfgang Glas wrote: > On 2010-09-15 10:50, Ozkan Sezer wrote: >> On Wed, Sep 15, 2010 at 11:33 AM, Wolfgang Glas<[email protected]> >> wrote: >>> You might call it packagers' fate, however we have a couple of productive >>> packages out there, which build and run very well with gcc-4.4 ;-) >> >> Out of curiosity, are those packages failing with newer gcc, or are you >> just being strict for choosing the compiler version? > > It took us a hell lot of time to build up a debian repository > (http://deb.clazzes.org) with mingw-w64,zlib,libxml,omniorb,libpng,libtiff,qt4 > etc. and we're happy that all this stuff plays together well and is stable, > where stable means more than having a stable compiler toolchain. > > So we did not have the time to play with gcc-4.5.x for now. Moreover, it's not > so easy to keep up to date with all the different packaging philosophies out > there, we have mingw-w64 snapshots, sezero, TDM, dimitij Ledkovs's debian > packaging efforts.... > > ....many ways to get confused :-/ >
Be warned that gcc 4.x.x-4.5.0 ABI is not compatible with future versions. From 4.5.1 and 4.6.x onwards, 64-bit symbols do not have the "_" prefix. Binutils CVS (2.20.51 as of writing) is also needed. As for different builds, the autobuilds are as vanilla as possible without any patches, meant for testing but it is usable. sezero builds do get some attention from Ozkan, so its mostly OK. I can't say much for the other builds though. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
