On 9/15/19 8:14 PM, 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.

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`


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.

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.

However, I am still unable to install Qt5WebEngine. While the above fixes my first issue that caused a build failure, I am now experiencing yet another build failure MUCH later into the process. Here is the output:

`In member function ‘void SocketCanBackend::readSocket()’:
socketcanbackend.cpp:697:41: error: ‘SIOCGSTAMP’ was not declared in this scope
          if (Q_UNLIKELY(ioctl(canSocket, SIOCGSTAMP, &timeStamp) < 0)) {


I think you missed an instruction in LFS, glibc:

sed -i '/asm.socket.h/a# include <linux/sockios.h>' \
   sysdeps/unix/sysv/linux/bits/socket.h

Since it is already installed you can probably do. as root

sed -i '/asm.socket.h/a# include <linux/sockios.h>' \
   /usr/include/bits/socket.h

----

To bottom, post in gmail, after you click on reply, click on the three vertical dots. Then navigate to the end of the message. It also helps to trim the message to what you are replying to, including the footer.

In most email clients, the footer is recognized by the email signature delimiter where it *starts* as dash dash space and is not included in a reply. Gmail does not automatically remove footers from replies.

  -- Bruce


--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to