On Fri, May 06, 2016 at 02:33:45PM -0500, Douglas R. Reno wrote:
> On May 6, 2016 1:57 PM, "Ken Moffat" <[email protected]> wrote:
> >
> Qtwebengine will be interesting. I don't have LXQt in systemd, so I don't
> have Qupzilla. I was considering adding it though.

I do not normally build lxqt, but I do use qupzilla as my second
browser.  In this case, the problem appears to be related to a
change in nss-3.23.  The bug report is at
https://bugreports.qt.io/browse/QTBUG-51890 - the mozilla mercurial
changeset being blamed is
https://hg.mozilla.org/projects/nss/rev/b7b1d793bc64 which changes a
lot of things.  I've started a build with the patch, it uses ssl
(possibly, a bundled 'boringssl' - if so, that is the last thing we
really need : but it calls it openssl in config/linux.pri) instead of
nss for cryptography and nss only for certificate handling so I don't
think it is similar to the other problems.

If it works, I might need advice on the patch name -
qt-everywhere-opensource-src-5.6.0-qtwebengine_nss-1.patch looks a
bit long.

> 
> I wonder if we just have to force it to use C99/C++98 like we have to for
> other packages. When I build Qt5 tomorrow (I hope), I will try that and
> report back.
> 
> Douglas R. Reno

But I did get a somewhat similar firefox-46.0 build failure on one
of my old systems - didn't manage to get that sort of fix to work,
and I have not yet looked at my other old systems.

It was in js/src/builtin/Intl.cpp -
In function 'js::ImmutablePropertyNamePtr JSAtomState::* 
GetFieldTypeForFormatField(UDateFormatField)':
/scratch/working/firefox-46.0/js/src/builtin/Intl.cpp:2145:12:
error: 'UDAT_TIME_SEPARATOR_FIELD' was not declared in this scope
       case UDAT_TIME_SEPARATOR_FIELD:
            ^

At that time google had nothing relevant, I guess I'll take another
look sometime in the next few weeks :)

ĸ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

Reply via email to