I previously had successfully compiled qt-gui using - gcc-4.7 - glibc-2.16 --- emerge -pqv qt-gui [ebuild R ] x11-libs/qt-gui-4.8.4 USE="accessibility c++0x cups dbus gif glib gtkstyle mng pch qt3support tiff xinerama xv (-aqua) -debug -egl -exceptions -nas -nis -trace" --- Portage 2.1.11.50 (default/linux/amd64/10.0/desktop/kde, gcc-4.7.2, glibc-2.17, 3.7.4-1046.cfr x86_64) ================================================================= System Settings ================================================================= System uname: Linux-3.7.4-1046.cfr-x86_64-Intel-R-_Core-TM-2_Duo_CPU_P8700_@_2.53GHz-with-gentoo-2.2 KiB Mem: 3763724 total, 66296 free KiB Swap: 5058080 total, 4753744 free Timestamp of tree: Fri, 25 Jan 2013 14:15:01 +0000 ld GNU ld (GNU Binutils) 2.23.1 app-shells/bash: 4.2_p42 dev-java/java-config: 2.1.12-r1 dev-lang/python: 2.7.3-r3, 3.2.3-r2 dev-util/cmake: 2.8.10.2-r1 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.6 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.9.6-r3, 1.11.6, 1.13.1 sys-devel/binutils: 2.23.1 sys-devel/gcc: 4.7.2 sys-devel/gcc-config: 1.8 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.7 (virtual/os-headers) sys-libs/glibc: 2.17 Repositories:
Created attachment 336854 [details] build log
Because of these error messages: ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:240:60: error: ‘XEventClass’ has not been declared ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:429:5: error: ‘PtrXListInputDevices’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:430:5: error: ‘PtrXOpenDevice’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:431:5: error: ‘PtrXFreeDeviceList’ does not name a type I had the idea to try it with/without USE of xv and xinerama But had no luck .... I have no glimpse if glibc-2.17 is involved? How could that be ....
While I have no idea what the heck is going on, at least before the tinderbox built this correctly, so it's not going to be a glibc-2.17 problem... maybe libXi?
Created attachment 336896 [details] build.log using color n for convenience @Diego, uups, I had some x11 packages on hold at stable, because I didn't want to pull x11-base/xorg-server-1.13.1.901 x11-libs/libXi-1.6.2 Now I upgraded all to Gentoo~unstable, but no luck.
mmm nice... neither QT_TABLET nor QT_NO_TABLET are defined, thus QT_NO_TABLET gets automatically defined by qconfig.h and XInput.h is not included, therefore causing the build error. This should not matter when building qt-gui itself though, so I need to find out why it fails for you...
@Davide, I watch: What shall I try? How I said earlier, I did recompile a few weeks before portage -e world when I change to gcc-4.7.2 successfully. But now with glibc-2.17 ... Or did I do something wrong otherwise before ...
I added the missing QT_TABLET define, please sync in a couple of hours and retry.
Just curiousity: All of qt is TABLET but headless server?
@Davide, No it doesn't help. I can diff the build logs, no difference at all! I just wanted to downgrade glibc, just in case it has some very weird thing to do with it, because I had compiled qt-gui just weeks before. But I am not supposed to do a downgrade (I thought I can manage from a Debian chroot with pkgdir/sys-libs/glibc-2.17.tbz2 at hand): * Downgrading glibc is not supported and a sure way to destruction * ERROR: sys-libs/glibc-2.16.0 failed (setup phase):
Now another try: I had changed the USE flag -c++0x and emerge -avDN world, which resulted rebuild of x11-libx/qt* But no luck, the same error out at: Emerging (7 of 13) x11-libs/qt-gui-4.8.4 As ever: In file included from ../../include/QtGui/private/qt_x11_p.h:1:0, from inputmethod/qinputcontextfactory.cpp:65: ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:236:43: error: ‘XDevice’ has not been declared ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:237:9: error: ‘XDeviceInfo’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:238:9: error: ‘XDevice’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:239:36: error: typedef ‘PtrXFreeDeviceList’ is initialized (use decltype instead) ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:239:36: error: ‘XDeviceInfo’ was not declared in this scope ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:239:49: error: expected primary-expression before ‘)’ token ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:240:60: error: ‘XEventClass’ has not been declared In file included from ../../include/QtGui/private/qt_x11_p.h:1:0, from inputmethod/qinputcontextfactory.cpp:65: ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:429:5: error: ‘PtrXListInputDevices’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:430:5: error: ‘PtrXOpenDevice’ does not name a type ../../include/QtGui/private/../../../src/gui/kernel/qt_x11_p.h:431:5: error: ‘PtrXFreeDeviceList’ does not name a type make: *** [.obj/release-shared/qinputcontextfactory.o] Error 1
Created attachment 337594 [details] emerge-info ... I missed to upload any complete emerge --info No one can reproduce this build failure? Anyone: Do you use - glibc-2.17 - gcc-4.7.2 and build successfully qt-gui? What diff to my emerge --info might be there - any cause?
(In reply to comment #11) > Created attachment 337594 [details] > emerge-info > > ... I missed to upload any complete emerge --info > > No one can reproduce this build failure? > Anyone: Do you use > - glibc-2.17 > - gcc-4.7.2 > and build successfully qt-gui? > What diff to my emerge --info might be there - any cause? I had the same problem using gcc-4.6.3. Per coincidence I downgraded pkg-config to 0.27.1 and then it emerged flawlessy. With pkgconfig-0.28 I had no luck. Which version of pkgconfig or pkgconf are you using?
(In reply to comment #12) > (In reply to comment #11) > > Created attachment 337594 [details] > > emerge-info > > > > ... I missed to upload any complete emerge --info > > > > No one can reproduce this build failure? > > Anyone: Do you use > > - glibc-2.17 > > - gcc-4.7.2 > > and build successfully qt-gui? > > What diff to my emerge --info might be there - any cause? > > I had the same problem using gcc-4.6.3. Per coincidence I downgraded > pkg-config to 0.27.1 and then it emerged flawlessy. With pkgconfig-0.28 I > had no luck. Which version of pkgconfig or pkgconf are you using? i can confirm that qt-gui-4.8.4 compiles fine with pkgconfig-0.27.1. with pkgconfig-0.28 i have failure
The same here: i can confirm that qt-gui-4.8.4 compiles fine with pkgconfig-0.27.1. with pkgconfig-0.28 i have failure So, this bug should be assigned against pkgconfig-0.28
*** Bug 455484 has been marked as a duplicate of this bug. ***
I cannot reproduce by simply updating to pkgconfig-0.28 and then rebuild qt-gui, so something else must be involved... Can you provide a list of all packages you emerged *after* you updated to pkgconfig-0.28 please? Something like: sed -n '/completed emerge.*dev-util\/pkgconfig-0\.28/,$ s/^.*completed emerge //p' /var/log/emerge.log
@Davide, simply all: I made a glibc-2.17 upgrade and did an emerge -e world
(In reply to comment #17) > @Davide, simply all: I made a glibc-2.17 upgrade and did an emerge -e world ouch! that's useless then :/ anyone else who did _not_ do an emerge -e world?
(In reply to comment #18) > (In reply to comment #17) > > @Davide, simply all: I made a glibc-2.17 upgrade and did an emerge -e world > > ouch! that's useless then :/ anyone else who did _not_ do an emerge -e world? here is my list http://dev.gentoo.org/~hwoarang/pkgconf-list.txt
Awesome! libXi is my first suspect, can you attach its .pc file please?
Created attachment 338142 [details] xi.pc here it is
My xi.pc is exactly the same. After upgrading to todays ~unstable xorg-server icu and cairo and the now stable pkgconfig-0.28 the failing qt-gui build log ends a bit different: --- image/qpixmap_x11.cpp:161:20: Fehler: »appDisplay« ist kein Element von »QX11Info« image/qpixmap_x11.cpp: In Funktion »bool qt_create_mitshm_buffer(const QPaintDevice*, int, int)«: image/qpixmap_x11.cpp:176:25: Fehler: »const class QPaintDevice« hat kein Element namens »data« image/qpixmap_x11.cpp: In Elementfunktion »virtual QPixmap QX11PixmapData::transformed(const QTransform&, Qt::TransformationMode) const«: image/qpixmap_x11.cpp:1922:51: Fehler: »const QX11PixmapData* const« kann nicht nach »const QPaintDevice*« für Argument »1« nach »bool qt_create_mitshm_buffer(const QPaintDevice*, int, int)« umgewandelt werden image/qpixmap_x11.cpp:1926:41: Warnung: Vergleich zwischen vorzeichenbehafteten und vorzeichenlosen Ganzzahlausdrücken [-Wsign-compare] image/qpixmap_x11.cpp:1926:65: Warnung: Vergleich zwischen vorzeichenbehafteten und vorzeichenlosen Ganzzahlausdrücken [-Wsign-compare] image/qpixmap_x11.cpp:1947:37: Fehler: »white« wurde in diesem Gültigkeitsbereich nicht definiert image/qpixmap_x11.cpp:1947:37: Anmerkung: empfohlene Alternative: In file included from /usr/include/qt4/QtCore/qobjectdefs.h:45:0, from /usr/include/qt4/QtCore/qobject.h:47, from /usr/include/qt4/QtCore/qcoreapplication.h:45, from kernel/qt_gui_pch.h:61: /usr/include/qt4/QtCore/qnamespace.h:108:9: Anmerkung: »Qt::white« ...
(In reply to comment #22) > My xi.pc is exactly the same. > After upgrading to todays ~unstable xorg-server icu and cairo and the now > stable pkgconfig-0.28 the failing qt-gui build log ends a bit different: > --- > image/qpixmap_x11.cpp:161:20: Fehler: »appDisplay« ist kein Element von > »QX11Info« > image/qpixmap_x11.cpp: In Funktion »bool qt_create_mitshm_buffer(const > QPaintDevice*, int, int)«: > image/qpixmap_x11.cpp:176:25: Fehler: »const class QPaintDevice« hat kein > Element namens »data« > image/qpixmap_x11.cpp: In Elementfunktion »virtual QPixmap > QX11PixmapData::transformed(const QTransform&, Qt::TransformationMode) > const«: > image/qpixmap_x11.cpp:1922:51: Fehler: »const QX11PixmapData* const« kann > nicht nach »const QPaintDevice*« für Argument »1« nach »bool > qt_create_mitshm_buffer(const QPaintDevice*, int, int)« umgewandelt werden > image/qpixmap_x11.cpp:1926:41: Warnung: Vergleich zwischen > vorzeichenbehafteten und vorzeichenlosen Ganzzahlausdrücken [-Wsign-compare] > image/qpixmap_x11.cpp:1926:65: Warnung: Vergleich zwischen > vorzeichenbehafteten und vorzeichenlosen Ganzzahlausdrücken [-Wsign-compare] > image/qpixmap_x11.cpp:1947:37: Fehler: »white« wurde in diesem > Gültigkeitsbereich nicht definiert > image/qpixmap_x11.cpp:1947:37: Anmerkung: empfohlene Alternative: > In file included from /usr/include/qt4/QtCore/qobjectdefs.h:45:0, > from /usr/include/qt4/QtCore/qobject.h:47, > from /usr/include/qt4/QtCore/qcoreapplication.h:45, > from kernel/qt_gui_pch.h:61: > /usr/include/qt4/QtCore/qnamespace.h:108:9: Anmerkung: »Qt::white« > ... Please attach the full build.log (and in the *english* language)
Created attachment 338160 [details] qt-gui-4.8.4-build.log in english
(In reply to comment #24) > Created attachment 338160 [details] > qt-gui-4.8.4-build.log in english That's caused by QT_MITSHM, which I removed again now. Please retry in a couple of hours.
If it still fails, please attach your /usr/include/qt4/Gentoo/gentoo-qconfig.h
Created attachment 338394 [details] built log - compile failed again for -r1
Created attachment 338396 [details] gentoo-qconfig.h as asked @Davide, Do you want to see any old gentoo-qt-gui-qconfig.h of the qt-gui ebuild I previously compiled with the old dev-util/pkgconfig-0.27.1 ?
similar bug: https://bugs.gentoo.org/show_bug.cgi?id=456286 There are two people having the build failure. This pops up the question what is the difference: @Davide, why does your system not reproduce the failure? I have an abstruse suspicion: In the aftermath of the transition to the new eapi 5 I had observed my system to not having upgraded all of the libs, here: https://forums.gentoo.org/viewtopic-t-947732-highlight-.html I have used the there puplished my script to find this out. I then thought it was my use of prelink at the time before ... Perhaps it is your system having some old libs which provide a qt-gui build going?
Please please please... remove "--quiet" from MAKEOPTS and never add it again. Your build logs are completely useless. You can use emerge --quiet-build if you don't want to see build output, still producing useful build logs.
Created attachment 338446 [details] build.log noQuiet Eng noColor
Do you have x11-libs/cairo built with USE=qt4 ?
Yes: [ebuild R ] x11-libs/cairo-1.12.12 USE="X glib qt4 svg xcb (-aqua) -debug -directfb -doc (-drm) (-gallium) -legacy-drivers -opengl -openvg -static-libs"
Awesome, found the issue. With cairo[qt4], cairo.pc is pulling in /usr/include/qt4 before (almost) everything else, thus the installed qt4 headers are used instead of the ones from ${S} (qconfig.h and gentoo-qconfig.h in particular). So, rebuild cairo with USE=-qt4 and then rebuild qt-gui. This should solve at least the MITSHM issue, maybe also the XInput one.
@Davide, awesome you found the issue! Qt-gui just compiled having cairo[-qt]. I see you have been sure enough to already put the hint about it into the qt-gui.ebuild. Why the hell does pkgconfig<0.28 not produce the failure? Is the new stable pkgconfig-0.28 just a bit more correctly doing its work? Was there builtin some workaround into the previous pkgconfig?
*** Bug 456286 has been marked as a duplicate of this bug. ***
(In reply to comment #34) > Awesome, found the issue. > > With cairo[qt4], cairo.pc is pulling in /usr/include/qt4 before (almost) > everything else, thus the installed qt4 headers are used instead of the ones > from ${S} (qconfig.h and gentoo-qconfig.h in particular). > > So, rebuild cairo with USE=-qt4 and then rebuild qt-gui. This should solve > at least the MITSHM issue, maybe also the XInput one. yes that fixes it. So what's the real bug here?
cairo[qt4] enables the experimental qt4 backend for cairo, that probably nobody needs. After discussion with Davide, I have masked this useflag for all versions of cairo. This should fix the present issue. So users who hit this, should sync, rebuild cairo (with qt4 useflag disabled) and then should be able to build qt-gui without problem.
Additionally, qt-gui[gtkstyle] now depends on cairo[-qt4], to ensure the problem will never appear again.
*** Bug 456756 has been marked as a duplicate of this bug. ***
