On Tue, May 10, 2016 at 03:23:31PM +0200, Pierre Labastie wrote:
> On 10/05/2016 11:44, Pierre Labastie wrote:
> > On 10/05/2016 11:10, Pierre Labastie wrote:
> > > On 10/05/2016 08:59, Pierre Labastie wrote:
> > > > On 10/05/2016 06:00, Ken Moffat wrote:
> > > > > Last week I uploaded a patch for qtwebengine. Since then, qt5 has
> > > > > been updated to note that only QupZilla (instead of nothing) uses
> > > > > qtwebengine.
> > > > >
> > > > > BUT: I want to add the patch to the book, so that anybody else who
> > > > > builds QupZilla can get the damned thing to build. Meanwhile, I'm
> > > > > still on gcc-5, probably for the rest of this week, and I see that
> > > > > qt5 has been tagged for gcc-6 : but I have no idea if that is true
> > > > > for the patched build of qtwebengine.
> > > > >
> > > > > What should I do ?
> > > > >
> > > > > ĸen
> > > > Hi Ken,
> > > >
> > > > I've tagged qt5 for GCC 6, because it builds fine (without
> > > > qtwebengine) on GCC 6.
> > > > I'll be happy to test the patch with GCC 6. I understand it is
> > > > in the patch repo, isn't it?
> > > >
> > > > I'll do that this afternoon.
> > > >
> > > > Regards
> > > > Pierre
> > > >
> > > Note that the tag was without qtwebengine (patched or not).
> > >
> > > Pierre
> > First issue : qtwebengine needs libpci.
> > Second issue : here is what I get from "make module-qtwebengine", just
> > before it fails:
> > ---------
> > [...] not relevant anymore [...]
> > --------
> > It is with GCC 6, and using the patch.
> > I am currently trying after adding pciutils.
> >
> Added pciutils allowed the build to pass : here is what I have now:
> ----------
> cd qtwebengine/ && ( test -e Makefile ||
> /sources/qt5/qt-everywhere-opensource-src-5.6.0/qtbase/bin/qmake
> /sources/qt5/qt-everywhere-opensource-src-5.6.0/qtwebengine/qtwebengine.pro
> -o Makefile ) && make -f Makefile
> Info: creating cache file
> /sources/qt5/qt-everywhere-opensource-src-5.6.0/qtwebengine/.qmake.cache
> Running configure tests
> Checking for khr... yes
> Checking for libcap... yes
> Checking for snappy... no
> Checking for srtp... no
> System zlib or minizip not found. Using Chromium's copies.
> System libwebp or libwebpdemux not found. Using Chromium's copies.
> System libevent not found. Using Chromium's copy.
> System jsoncpp not found. Using Chromium's copy.
> System opus not found. Using Chromium's copy.
> System vpx >= 1.4 not found. Using Chromium's copy.
> System libsrtp not found. Using Chromium's copy.
> System snappy not found. Using Chromium's copy.
> SSL............................... Using system NSS
> ICU............................... Using internal copy (Default, force
> system ICU with WEBENGINE_CONFIG += use_system_icu)
> FFMPEG............................ Using internal copy (Default, force
> system FFMPEG with WEBENGINE_CONFIG += use_system_ffmpeg)
> Proprietary codecs (H264, MP3).... Not enabled (Default, enable with
> WEBENGINE_CONFIG += use_proprietary_codecs)
> make[1] : Entering directory
> "/sources/qt5/qt-everywhere-opensource-src-5.6.0/qtwebengine" [...]
> --------------------
> Note that neither libwebp nor libevent, opus or libvpx is installed on my
> system. I'll have to try with those. I think jsoncpp, libsrtp, and snappy
> are not in the book. I guess the book instructions should include some
> "WEBENGINE_CONFIG" setting.
>
> WIth this, I've been able to build qupzilla, but when I move the mouse (or
> sometimes without moving the mouse but just after a while), the page
> disappears with a message "Something went wrong while loading this page".
>
> Pierre
Pierre,
Many thanks for testing. I've been doing other things, didn't
expect this to be done for me.
I didn't get any of those messages:
Info: creating super cache file
/scratch/working/qt-everywhere-opensource-src-5.6.0/.qmake.super
Qt is now configured for building. Just run 'make'.
Once everything is built, you must run 'make install'.
Qt will be installed into /opt/qt5
Under the 'Build options:' above that, the following are 'no' for my
build -
Using gold linker....... no
Use system proxies ..... no
ALSA ................... no
(that looks odd, I've got working alsa)
libinput................ no
Logging backends:
journald ............... no
syslog ............... no
libproxy.............. no
PulseAudio ............. no
DirectFB ............. no
EGLFS i.MX6 ........ no
EGLFS i.MX6 Wayland. no
EGLFS EGLDevice .... no
EGLFS Mali ......... no
EGLFS Raspberry Pi . no
Mir client............ no
Xi ................. no
SQL drivers:
DB2 .................. no
InterBase ............ no
MySQL ................ no
OCI .................. no
ODBC ................. no
SQLite 2 ............. no
TDS .................. no
tslib .................. no
Of the things you had reported :
zlib or minizip not found. Using Chromium's copies.
That seems odd - isn't zlib part of LFS itself ?
libwebp or libwebpdemux not found. Using Chromium's copies.
No message, and at that time I did not have libwebp.
libevent - system
jsoncpp not found. Using Chromium's copy.
If that is json-c, I did not have it at that time.
opus not found. Using Chromium's copy.
I don't have it.
vpx - system
libsrtp not found. Using Chromium's copy.
snappy not found. Using Chromium's copy.
I've not heard of either of those two.
SSL............................... Using system NSS
The problem was with system nss, so that proves the patch fixed it.
ICU - system
FFMPEG - system
I configured with:
-prefix /opt/qt5 -sysconfdir /etc/xdg -confirm-license -opensource
-dbus-linked -openssl-linked -system-harfbuzz -nomake examples
-no-rpath -optimized-qmake
For qupzilla, I opened 5 tabs after I started to reply, used them a
bit, tried slashdot, checked my own website and looked at a text file
there, logged in to lwn.net. Then I came back to this and put in the
details. After that I went back to qupzilla, read things, clicked on
links, scrolled down. No problems.
With previous versions qupzilla occasionally crashed on some links.
ĸen
--
This email was written using 100% recycled letters.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
