x11-libs/qt-gui-4.7.9999 from qting-edge failed to compile. Reproducible: Always
Created attachment 226817 [details] build log
Created attachment 226819 [details] emerge --info output
Created attachment 226821 [details] emerge -pqv output
Stable branch just got a huge update the other day, so we need to have a look at the ebuilds again. The ebuilds for the declarative and assistant modules also have problems.
Just for the record: I tried emering qt-gui (and the whole qt) several times without success. Now I tried the 4.7 branch (not the 4.7-stable one - i.e. without the stable-branch useflag) and this one compiles successful.
I rebuild the whole stable branch yesterday and it did work for me. I will try again today just in case I missed something :/
Ok correct me if I am wrong the rule make docs doesnt generate html documentation according to makefile docs: adp_docs qch_docs However, the install_htmldocs rule is the following install_htmldocs: FORCE @$(CHK_DIR_EXISTS) $(INSTALL_ROOT)/usr/share/doc/qt-4.6.9999/ || $(MKDIR) $(INSTALL_ROOT)/usr/share/doc/qt-4.6.9999/ -$(INSTALL_FILE) /var/tmp/portage/x11-libs/qt-core-4.6.9999/work/qt-everywhere-opensource-src-4.6.9999/doc/html $(INSTALL_ROOT)/usr/share/doc/qt-4.6.9999/ But the doc/html doesnt exist. The html documentation doesnt exist on live ebuild because simply upstream nor ships it neither has a rule to generate it If there are no objections the live ebuilds should be fixed to NOT bother about the html docs at all
Ingore my last comment. I just posted on wrong bug :/
I rebuild the whole stable-branch a couple of hours ago. Still no problem for me
qt-gui-4.7.9999 failed to compile for me too.
Please update your qting-edge overlay clone, your portage tree, delete /usr/portage/distfiles/git-src/qt-4.7.9999 and try again It works for me on 3 different machines
Created attachment 228231 [details] Makeshift The patch for those is to be gathered no coma. It will be not correctly assured that it to work, but is gathered.
Problem that eglCreateImageKHR is not declared in that in EGL/egl.h, but declared in EGL/eglext.h
-stable-branch works so I assume that the stable-branch needs to be bumped from upstream in order to have a fully working stable-branch again I will test your patch and commit it if needed
Patch applied Please verify that it works
Upstream didn't update Qt stable branch since April 04 2010 [1]. I think the stable-branch use flags should be removed since it is actually more instable and prone to build errors. PS: qt-gui patches are only applied to 4.7.9999 and not 4.9999. Using stable-branch, both ebuilds fails with or without patches. [1] http://www.qt.gitorious.org/qt/qt/commits/4.7-stable
(In reply to comment #16) > Upstream didn't update Qt stable branch since April 04 2010 [1]. > I think the stable-branch use flags should be removed since it is actually more > instable and prone to build errors. > > PS: qt-gui patches are only applied to 4.7.9999 and not 4.9999. > Using stable-branch, both ebuilds fails with or without patches. > > [1] http://www.qt.gitorious.org/qt/qt/commits/4.7-stable > Build.log please As you can see here, i did build [stable-branch] quite recently http://dev.gentoo.org/~hwoarang/qt/qt4-live-status
Created attachment 234785 [details] build log This is exactly the same build log since Qt stable is not updated. I don't see the point in maintaining support for a random git commit while [-stable-branch] compiles fine.
(In reply to comment #18) > Created an attachment (id=234785) [details] > build log > > This is exactly the same build log since Qt stable is not updated. > I don't see the point in maintaining support for a random git commit while > [-stable-branch] compiles fine. > I can't reproduce it . What is the status of the egl use flag. Do you have it enabled?
I added an additional warning when building stable-branch 4.7.9999 or higher http://gitorious.org/gentoo-qt/qting-edge/commit/fbc9e2dbabc0cf388c1fa7f17171e0099abfe57f I have to talk to the rest of the team to discuss about this branch thought Thanks for pointing this out
Ok, I had typed a long message explaining the problem, but it seems you understood it now. Maybe I confused you by reusing this bug :) By the way, qt-gui-4.9999 doesn't have the egl use flag here.
(In reply to comment #21) > Ok, I had typed a long message explaining the problem, but it seems you > understood it now. Maybe I confused you by reusing this bug :) > By the way, qt-gui-4.9999 doesn't have the egl use flag here. > I do understand the problem but I cannot reproduce the build failures
Do you still have problems emerging qt live ebuilds from qting-edge?
