Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,154
Original Poster
Rep:
Definitely a problem with python 2 being built in chroot, rebuilding in the 'real' system works, so gonna mark this solved, thanks Luridis.
Just an after thought but as python 3 is part of the basic LFS system now and has to be built in chroot is it prone to the same problems and does it need to be rebuilt when booted to the 'real' system?
Distribution: LFS 9.0 Custom, Merged Usr, Linux 4.19.x
Posts: 616
Rep:
Quote:
Originally Posted by Keith Hedger
Just an after thought but as python 3 is part of the basic LFS system now and has to be built in chroot is it prone to the same problems and does it need to be rebuilt when booted to the 'real' system?
I don't know, I always rebuild them once berkeley, etc. is installed. What you can do is look at the compilation summary at the end, it usually lists modules that couldn't be built.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,154
Original Poster
Rep:
Unfortunately cleared out my logs from then but maybe someone else has kept that info.
Don't know if this is the module, it looks like it going by the name:
/usr/lib64/python3.7/lib-dynload/_multiprocessing.cpython-37m-x86_64-linux-gnu.so
Distribution: LFS 9.0 Custom, Merged Usr, Linux 4.19.x
Posts: 616
Rep:
I just checked the Modules/_multiprocessing directory of both Python 3.8.0 and 2.7.17 when built in chroot. While the build summary didn't mention it, there were no .o files in that directory for either version. So the answer is yes, Python is less than complete when built in chroot.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,154
Original Poster
Rep:
Quote:
Originally Posted by Luridis
I just checked the Modules/_multiprocessing directory of both Python 3.8.0 and 2.7.17 when built in chroot. While the build summary didn't mention it, there were no .o files in that directory for either version. So the answer is yes, Python is less than complete when built in chroot.
thanks for that ( sorry for late reply, been ill ), I have always built most of my system in chroot, quess I'm gonna have to change that, which is a big PITA, oh well life is change!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.