> Sent: Monday, September 16, 2019 at 3:29 PM > From: "Pierre Labastie via blfs-support" > <[email protected]> > To: [email protected] > Cc: "Pierre Labastie" <[email protected]> > Subject: Re: [blfs-support] Issue installing Python2 module for Jinja2-2.10.1 > > On 16/09/2019 03:14, Jared Stevens via blfs-support wrote: > > (If I am continuing to top-post still, would someone be able to tell me the > > proper way to reply to the thread? Currently, I am simply clicking "Reply" > > in > > Gmail to the latest email in the thread that I have) > > > > Just to provide an update for you all, I uninstalled Python 2 and > > reinstalled > > it along with all modules in the book (without pip) with no change. > > For me, after installing MarkupSafe 1.1.1 for python2 with the book > instructions (recently added in trunk, amount to what you have below), Jinja2 > finds it. > > > > > So after digging deeper into the log, I decided to visit Debian's package > > repository site for their Jessie distribution and downloaded the source > > tarbell for MarkupSafe-0.23 just for the heck of it. > > > > I installed it identically to how the book installs MarkupSafe-1.1.1 except > > I > > installed the Python 2 module instead like so: > > > > `python2 setup.py build && > > > > python2 setup.py install --optimize=1` > > > > > > What is the difference with what was in the book (apart from the obvious one > which is to use python2)? Have you used those instructions for MarkupSafe > 1.1.1 (with python2, I mean)? > > > Afterwards, I attempted the Jinja2 module install again. This time, it was > > able to "see" the MarkupSafe module and used 1.1.1 to successfully install > > the > > Python 2 module. > > Could it be that, for some reason, easy-install.pth had not been updated when > installing MarkupSafe 1.1.1, but got updated when installing 0.23? > > > > > So it appears that installing MarkupSafe-0.23 allows for Jinja2 to find the > > most recent version of MarkupSafe installed (which is 1.1.1) when building > > the > > Python 2 module. > > I understand you are building in chroot. Does the network name resolution > work? Maybe you have to edit /etc/resolv.conf. That may allow resolving the > name for pypi. > > Pierre > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
Hello, With regards to chroot, if you are using the systemd version of the book, there is no resolv.conf file, as it is a symlink to a differnet directory. I always remove the symlink and create a proper resolv.conf in /etc and this allows me to use the "host" ineternet connection. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
