On Sat, May 09, 2020 at 11:56:05PM +0100, Ken Moffat via blfs-support wrote:
> On Sat, May 09, 2020 at 10:56:46AM +, Tom Willhite via blfs-support wrote:
> >
> > From: blfs-support on
> > behalf of Ken Moffat via blfs-support
> >
> > Sent: Thursday, May 7, 2020 9:29 PM
> > To: blfs-support@lists.linuxfromscratch.org
> >
> > Cc: Ken Moffat
> > Subject: [blfs-support] Odd build failure with Jinja2 (now ok):wq
> >
>
> > I _thought_ I had deleted the files installed from the failed
> > Python2 build, but apparently I didn't. I then built Jinja2 for
> > Python3, and let my script continue, expecting qtwebengine to fail -
> > but that succeeded and falkon has now been built and is working.
> > So, it seems that the previous 2.7 install was ok (even though it
> > failed).
> >
> > - - -
> >
> > I've now tried a manual build, and installed to a DESTDIR equivalent
> > using
> > python2 setup.py install --root /tmp/JINJA2
> > and that completed ok.
>
> > I can confirm Jinja in blfs-sysd book is broke for the python2 version. V3
> > builds/installs. Same invalid syntax error as you posted Ken.
> > I'll chk back since I'd like it for qtwebengine but I think that builds ok
> > regardless of this error.
> >
> > Archetech
>
> Hi Tom,
>
> that is very interesting. I assumed the alpha version of MarkupSafe
> was the problem (probably never tested on a system with python2) and
> that it happened to have been removed, which was why my later manual
> build worked. But maybe there is again a newer version.
>
> Because I had NOT removed the 2.7 egg which did get installed, I
> think that was used by qtwebengine.
>
> That implies that for future builds Python2 Jinja is still needed,
> but might crap out in the later stages of the install - if so, not a
> problem. In other words, maybe add ' || true' to the Python2
> install and mark it down as collateral damage from the
> discontinuation of that version.
>
> But I don't know how pip works (maybe it uses mirrors, and if so thy
> might lag behind by a day or two).
>
> I'll bear this in mind, but I don't expect to be building
> qtwebengine on a fresh system for several weeks (and if 5.15 is
> released and I upgrade my existing systems I won't bother updating
> Jinja2).
>
I'm now running a new build (trying the cross-chap5 LFS branch) and
got as far as Jinja about 24 hours ago. The exact same failures in
the python2 install, which ended in error.
Unfortunately, I overwrote that log by allowing the py2 install to
fail - but it was definitely trying to install MarkupSafe in the 2.7
python site-packages. I'd forgotten about this, semes like much
more than 3 weeks ago.
So, at the moment all I know is that it *sometimes* fails when
trying to install MarkupSafe in the 2.7 site-packages. This is the
last version of Jinja2 to support Python2, so trying to debug it
seems a waste of time.
I think the problem is that for some reason easy_install decides
that MarkupSafe is needed (it never used to be, for python2) and
picks a current version which does not support python3.
In my own scripts (designed to error if a non-zero status is
unexpectedly encountered) I have added ' || true' to the pythin2
install command.
For the book, to support automation such as jhalfs I think we need
the same, with a Note above it that "Sometimes the python2 install
tries to install the incompatible and unnecessary current version of
MarkupSafe, and fails. As long as the files in
/usr/lib/python2.7/site-packages/Jinja2-2.11.2-py2.7.egg/jinja2 have
been installed, the install will be adequate for QtWebengine."
I'll create a ticket.
ĸen
--
Do you not know that, what you belittle by the name tree is but the
mere four-dimensional analogue of a whole multidimensional universe
which - no, I can see you do not. -- Druellae (a Dryad)
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
