On Sat, Apr 18, 2015 at 08:53:25PM -0300, Fernando de Oliveira wrote:
> On 18-04-2015 18:16, Ken Moffat wrote:
> 
> > For qt4, I did not run everything that is in the book (I'll do that if I
> > test kde on a second build), but I wish to draw this one to people's
> > attention because it appears to build fine without the patch, and in
> > double-quick time.  The problem is that the summary of the build
> > (about 110 lines down my log) shows that WebKit will not be built.
> > That bit me when I tried to build qupzilla (which is not in BLFS),
> > and I assume it will also bite anybody building kde4.
> 
> What patch?
> 
> I understand that using gcc5, WebKit will not be built.
> 
> Do you have the error log? I was thinking that it could be something to
> do with new glib, But just ran a DESTDIR build without problem.
> 
> Qupzilla didn't work fine here, with qt4. Opened the window, but any url
> or just return in the search bur made it crash.
> 
> Needed to build qt5 just for it.
> 
> qt-4.8.6
> qt5-5.4.1
> qupzilla-1.8.6-qt5
> 
Because qupzilla is not in BLFS, I only check occasionally to see if
there is a new version - so, I'm still on 1.8.5.  I've got enough
change to my scripts just trying to keep up with BLFS ;)

With qt5, the book's default instructions do not build Qt Web
Engine, but by omitting '-skip qtwebengine' (as in the Command
Explanations) it will do a fuller (and much longer) build.  I did
that a little while before 7.7, when I was testing to see if I could
drop Qt4 from my non-kde builds (no, I can't - vlc's graphic app
needs qt4).

Qupzilla-1.8.5/qt4 is working "as normal" here, even on gcc5 (I have
it configured, so it now opens at a home page of my choice).  The
phrase "as normal" means that if I leave it, it often crashes - but
it reconnects to where it was next time I start it.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to