this regard upstream bug 20236, wich make webkit mandatory, after webkit is set to yes there is a check that revert it to 'no' if xrender is disabled (which is by ebuild). After the fix it still fail but with a linking error (another bug) --- /g/ovl/qting-edge/x11-libs/qt-assistant/qt-assistant-4.8.0.ebuild 2011-12-17 11:36:28.550940964 +0000 +++ qt-assistant-4.8.0.ebuild 2011-12-17 14:52:47.655621447 +0000 @@ -63,7 +63,7 @@ } src_configure() { - myconf="${myconf} -no-xkb -no-fontconfig -no-xrender -no-xrandr + myconf="${myconf} -no-xkb -no-fontconfig -no-xrandr -no-xfixes -no-xcursor -no-xinerama -no-xshape -no-sm -no-opengl -no-nas-sound -no-dbus -iconv -no-cups -no-nis -no-gif -no-libpng -no-libmng -no-libjpeg -no-openssl -system-zlib -no-phonon @@ -74,7 +74,8 @@ # https://bugreports.qt.nokia.com//browse/QTBUG-20236 # Even though webkit option is included, we do not build # any targets - myconf="${myconf} -webkit" + # according to configure xrender is needed by webkit + myconf="${myconf} -xrender -webkit" qt4-build_src_configure }
I suspect the linking bug mentioned may depend on bug #395055 since I cannot build qt-declarative +webkit
The error that makes qt-assistant fail is this one: ======== cp: cannot stat `/var/tmp/paludis/x11-libs-qt-assistant-4.8.0/work/qt-everywhere-opensource-src-4.8.0/doc/html/examples-manifest.xml': No such file or directory ======== The "linking"-errors are just from qdoc, so documentation-related. They never make installation fail.
Created attachment 296411 [details] qt-everywhere-opensource-src-4.8.0-qtwebkit-glib231.patch thanks for clarification. I'also needed to apply this patch from the fedora qt-4.8.0-0.23.rc1.fc16.src.rpm
Created attachment 296413 [details] qt-4.8.0-0.23.rc1.fc16.src.tar.gz stripped archive from the srpm (images and qt tarball removed). There are a pair of interesting patches, notably: webkit-qtwebkit-2.2-no_Werror.patch qt-everywhere-opensource-src-4.8.0-QTBUG-22037.patch qt-everywhere-opensource-src-4.8.0-QUrl_toLocalFile.patch qt-everywhere-opensource-src-4.8.0-qtwebkit-glib231.patch
(In reply to comment #4) > qt-everywhere-opensource-src-4.8.0-QTBUG-22037.patch According to https://bugreports.qt.nokia.com/browse/QTBUG-22037 comment by Oswald Buddenhagen, the patch itself contains no error, but it >> unveils bugs in the usage of qlist << The applications that behave bad (e.g. crash) should be patched, not Qt. So I don't know if it is good to add this patch, only to make akregator etc. not crash.
being a long time gentoo user I do agree with comment #5 by Franz Fellner, but it can delay the qt-4.8 appearance in the portage tree, on the same bug is also stated that qt itself has problem with this optimization. Anyway I've been unable to install this release even after a certain amount of effort, and shifted on working with qt5 from git but not portge managed.
(In reply to comment #6) > on the same bug is also stated that qt itself has problem with this optimization. had problems - I think qt-4.8.0 would not have been released, if this change would have caused errors somewhere in Qt itself. > Anyway I've been unable to install this release even after a certain amount of effort Which problems did you run into? I did not have any problem, except this one. The simple cause: examples-manifest is not existent in the tarball. The simplest solution would be to patch qt-src/doc/doc.pri, removing all the work done with this manifest-file.
Created attachment 296563 [details] remove missing manifests from doc/doc.pri I don't have any idea, if this is the only solution, but it finally makes qt-assistant install. There are not problems in Qt Assistant, examples and demos got indexed, they are accessible through assistant. Should these manifests be existent in the .tar.gz, or do they get created on the fly during build? I grepped the sources and did not get any matches other then in doc.pri.
These files are either not generated at some point or simply missing, couldn't find anything either. I've applied the fix in the overlay, thanks :)
indeed it now compile for me too
