Does testbot's MingW miscompile winmm:midi tests?
saulius2 at ar.fi.lt
Sat Sep 11 05:53:29 CDT 2010
* On Fri, 10 Sep 2010, Joerg-Cyril.Hoehle at t-systems.com wrote:
> Now what to do next?
> - uninitialised memory issue?
> - bad MingW or includes on test.winehq?
> How do MingW on test.winehq and testbot.winehq differ?
Difference of primary interest would be in the compiler versions and then
in configure options, I guess.
Reports on test.wineh.org says the details :
| Build version
| Using built-in specs.
| Target: i586-mingw32msvc
| Configured with: /home/ron/devel/debian/mingw32/mingw32-4.2.1.dfsg/build_dir/src/gcc-4.2.1-2-dfsg/configure
| -v --prefix=/usr --target=i586-mingw32msvc --enable-languages=c,c++
| --enable-threads --enable-sjlj-exceptions --disable-multilib
| Thread model: win32
| gcc version 4.2.1-sjlj (mingw32-2)
But testbot.winehq.org seems to provide such full info . The only
stuff I can find is the name of the cross-compiler binary used:
Lets compare it to the first one:
So at least it's clear both compilers were built using different build
environments and different targets (msvc vs gcc; i586 vs i686).
Seems like testbot.winehq.org should be enhanced to be a bit verbose. Is
it's code available? I haven't found one in Wine's git repo .
More information about the wine-devel