rhel-6 remaining problem

Erik van Pienbroek erik at vanpienbroek.nl
Sat Jun 25 16:02:06 UTC 2011


Farkas Levente schreef op wo 22-06-2011 om 10:45 [+0200]:
> i still not be able to rebuild qtlockedfile (which is not needed for me:-)

Hi,

The mingw-qtlockedfile and mingw-qtsingleapplication packages were just
an experiment of mine and I don't have plans to propose it for inclusion
in Fedora, so nothing will be lost if you can't get them to build.

Anyway, the macros mingw32_qmake_qt4 and mingw64_qmake_qt4 both referred
to an invalid mkspecs name. I've just fixed this in the testing repo

> but they both use %{_qt4_qmake} which is defined in the native qt-x11
> pacakge (why the qt rpm macros defined in qt-x11??? imho it's a bug).

Sound like a bug to me too. I recommend you to file a bugreport for this

> if i use the in spec file version win32-g++-cross then another problem
> happened during build:
> ----------------------------------
> make[2]: Entering directory
> `/builddir/build/BUILD/qtlockedfile-2.4_1-opensource/buildlib'
> i686-w64-mingw32-g++ -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> --param=ssp-buffer-size=4 -mms-bitfields -O2 -Wall -DUNICODE
> -DQT_LARGEFILE_SUPPORT -DQT_NO_DEBUG -DQT_CORE_LIB
> -I"/usr/i686-w64-mingw32/sys
> -root/mingw/include/QtCore"
> -I"/usr/i686-w64-mingw32/sys-root/mingw/include" -I"../src" -I"release"
> -I"/usr/lib/qt4/mkspecs/win32-g++-cross" -o release/qtlockedfile.o
> ../src/qtlockedfile.cpp
> i686-w64-mingw32-g++ -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> --param=ssp-buffer-size=4 -mms-bitfields -O2 -Wall -DUNICODE
> -DQT_LARGEFILE_SUPPORT -DQT_NO_DEBUG -DQT_CORE_LIB
> -I"/usr/i686-w64-mingw32/sys
> -root/mingw/include/QtCore"
> -I"/usr/i686-w64-mingw32/sys-root/mingw/include" -I"../src" -I"release"
> -I"/usr/lib/qt4/mkspecs/win32-g++-cross" -o release/qtlockedfile_unix.o
> ../src/qtlockedfile_unix.cpp
<snip>

Are you sure that you've used the mkspecs name 'win32-g++-cross'? It
looks like it was trying to compile a unix-specific file which is an
indication that the platform guessing (based on the mkspecs name) didn't
work.

Kind regards,

Erik van Pienbroek





More information about the mingw mailing list