> - avoid putting boost sources in /usr/include - that directory is > normally managed by package system of your OS > - don't run build process with "sudo"
I have followed your advice and removed boost from include and unzipped it somewhere in my home directory. As I had been messing about with LD_LIBRARY_PATH to try and get Python working with the tutorial 'Hello world', I have put it back to where it should be.
root is happier as there is less space being taken up, and everything now works like a charm.
Thank you so much for your efforts,
> To: firstname.lastname@example.org > From: email@example.com > Date: Wed, 10 Aug 2016 22:21:20 +0300 > Subject: Re: [Boost-build] Mismatched versions of Boost.Build engine and core > > On 10-Aug-16 7:56 PM, Alex Durie wrote: > > > > alex@alex-Lenovo-IdeaPad-Z500 > > /usr/include/boost_1_61_0/libs/python/example/tutorial $ sudo bjam > > > > and I am still getting the error ERROR: rule "READLINK" unknown in > > module "link" > > I have attached the terminal output of this as well in case it's instructive > > Alex, > > the above invocation appears to use bjam that you have installed in your > system, and is rather old. I would suggest you use b2 that you've build > from source, which is probably located at > > /usr/include/boost_16_0/b2 > > It's not important for your problem, but in general, I would suggest > that you > > - avoid putting boost sources in /usr/include - that directory is > normally managed by package system of your OS > - don't run build process with "sudo" > > The way you do it now makes it easy to accidentally do something > undesirable to system directory. > > HTH, > Volodya > > > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build