[Partially Solved] [Compiling Qt 5.4] MingW Intrinsic / conflicting declaration of '__m64 _m_pswapd(__m64)' with 'C' linkage

SGaist

That I don't know, but you can try the "bug report system":http://bugreports.qt-project.org to see if it's something known

MeerMusik

[quote author="SGaist" date="1418243537"]That I don't know, but you can try the "bug report system":http://bugreports.qt-project.org to see if it's something known[/quote]

Will do a Bug Report later today. For now I have changed the Thread Title: It seems this Bug can not be solved from Digia's Side.

Thanks for trying to help anyway.
Oliver

MeerMusik

Evening.

The Bug Report in JIRA got closed as invalid as it turns out, I could not even compile it MSVC in the first run. Later it worked - too late. BR is closed now.

Anyway:
In addition, I filed a Bug Report yesterday at the MinGW64 SourceForge Project Site.

I could not find an answer yet, why that dumb Bug has made it back to the 4.9.x Branch of MinGW64 - and why I am still able to compile 5.3.2 (did a test compile just yesterday again with all Examples and Tests without any Problem; 5.4.0 still fails. Even when I try to Build it from Git.).

Some change in the Qt Framework must have made the Bug Fix in the Compiler invalid.

Oliver

SGaist

What's the link to the report ?

MeerMusik

Evening:

The Bug Report (its more like a quick Copy+Paste of this Thread) is here:
https://bugreports.qt-project.org/browse/QTBUG-43268

SGaist

Do you have all these versions of MinGW installed on your computer at the same time ?

MeerMusik

Nope. Of course not. I unzip the different Compiler Versions when I want to test them, to C:\MinGW32\

After that, I restart my PC (normally not necessary but Murphy strikes out of the blue) and do the usual compile tests.

MeerMusik

Morning Forum.

I finally found some time to test a few things out. Besides from the Compiler Bug:

If I disable Angle AND OpenGL completely, 5.4.0 got build. Very strange.
[BTW: If I disable both: Will my own Executables run? I dont think so or is there any kind of Alternative?]

Does Qt 5.4.0 need specific / newer DirectX Files than 5.3.2? Or does anyone know an Alternative to try out? Must I install the DirectX SDK and the Windows 7 and and Windows 8 SDK in a specific order? Like I said, I am out of Ideas.

I re-installed the Windows 7 OS, DirectX SDK (June 2010), Windows 7.1 SDK and the Windows 8.1 SDK fresh (in that particular Order). Windows Update says "No Updates Available".

5.3.2 (and older Versions) still compiles fine.

Thanks!

MeerMusik

Time for another check:

Compilation of the 64-bit Version of Libglesv2*.dll (and therefore Qt 5.4.0 64-bit as a whole) works.

32-bit keeps failing.

MeerMusik

Morning everybody.

After a few replies in the BugReport from Kai Köhne, I was able to build Qt 5.4.0 x86 with the '-opengl desktop' Switch:
@
-opensource -confirm-license -prefix d:\qt-build -skip webengine -opengl desktop -debug-and-release -icu -I C:\icu32bit\include -L C:\icu32bit\lib -openssl -I C:\OpenSSL-Win32\include -L c:\OpenSSL-Win32\lib\MinGW -platform win32-g++ -nomake tests
@

I also was finally able to build a 64-Bit Variant with '-opengl dynamic' with the following Switches:
@
-opensource -confirm-license -prefix d:\qt-build-64bit -skip webengine -opengl dynamic -debug-and-release -icu -I C:\icu64bit\include -L C:\icu64bit\lib -openssl -I C:\OpenSSL-64bit\include -L c:\OpenSSL-64bit\lib -platform win32-g++ -nomake tests
@

One Problem remains:
I can not do a '-Developer-Build' or even a normal Build with Tests. QMutex and QVariant will always give hundreds of '__machine__x86_declaration' errors. Which results in 'corelib cannot be build'. This is valid for MinGW x86 and MinGW x64.

When 5.4.1 is out, I will see if can disable QMutex and QVariant.

Both Compiler Versions (x86 Posix-DWARF and x64 Posix-SEH) are updated to 4.9.2-RtV3-Rev1.

In the end, it is a Problem with the Compiler and the double / triple call of 'Intrinsic.h' from the compiler Directory.

As this kind of Bug exists for a few years now, it seems that it will never be changed / fixed.

Only Solution / Work-Around for me is to switch to x64 completely in the long run. The main Userbase is still running a x86 OS. But this is another Long-Term-Wannabe-Problem.

Have a good one :)
Oliver

SGaist

Usually you don't build the tests even when doing a developer build it eats time and space for no real benefits unless you plan to run them all. If you need to run one or more of them just build them on a as needed basis

MeerMusik

[quote author="SGaist" date="1422491056"]Usually you don't build the tests even when doing a developer build it eats time and space for no real benefits unless you plan to run them all. If you need to run one or more of them just build them on a as needed basis[/quote]

Yeah I know and I wish it would work this way. But for some strange reason, the Switch 'developer-build' keeps ignoring '-nomake tests'.

I will look into customising some Makefiles when 5.4.1 is out.