[SOLVED] make error while compiling perl (LFSv7.2 Step 5.28)
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.
1) Did the make step actually stop after the errors shown? Or did it continue to run until you got this message: Everything is up to date. Type 'make test' to run test suite.?
2) Do you remove the extracted directory when you try again? I'm asking because of this:
Code:
Makefile out-of-date with respect to ../../lib/Config.pm ../../config.h
Cleaning current config before rebuilding Makefile...
make -f Makefile.old clean > /dev/null 2>&1
../../miniperl "-I../../lib" "-I../../lib" Makefile.PL "INSTALLDIRS=perl" "INSTALLMAN1DIR=none" "INSTALLMAN3DIR=none" "PERL_CORE=1" "LIBPERL_A=libperl.a"
Writing Makefile for Archive::Extract
==> Your Makefile has been rebuilt. <==
==> Please rerun the make command. <==
The only way I can recreate that is by:
- extracting the perl package
- running all the steps (except the install part)
- going to $LFS/sources and extract the perl package again (without removing the perl directory)
- run the steps again.
Now I see these errors you show in your first post.
1) Did the make step actually stop after the errors shown? Or did it continue to run until you got this message: Everything is up to date. Type 'make test' to run test suite.?
2) Do you remove the extracted directory when you try again? I'm asking because of this:
Code:
Makefile out-of-date with respect to ../../lib/Config.pm ../../config.h
Cleaning current config before rebuilding Makefile...
make -f Makefile.old clean > /dev/null 2>&1
../../miniperl "-I../../lib" "-I../../lib" Makefile.PL "INSTALLDIRS=perl" "INSTALLMAN1DIR=none" "INSTALLMAN3DIR=none" "PERL_CORE=1" "LIBPERL_A=libperl.a"
Writing Makefile for Archive::Extract
==> Your Makefile has been rebuilt. <==
==> Please rerun the make command. <==
The only way I can recreate that is by:
- extracting the perl package
- running all the steps (except the install part)
- going to $LFS/sources and extract the perl package again (without removing the perl directory)
- run the steps again.
Now I see these errors you show in your first post.
yes the make step stops after showing that error , it does not go on further .
HATS OFF TO spiky0011 and druuna !!! THANKS ALOT FOR HELPING SO MUCH !!
i extracted it as lfs user and it compiled successfully and now m going ahead to run a test suite...
i hope i dont get error when i chroot the environment and try to install linux kernel headers ...
One question : Will it affect the lfs system if i compile and install perl first and then all other utilities like binutils , glibc , gcc in chapter 2 ( i.e. Temporary tools ) ???
I see
drwxr-xr-x. 30 aashay aashay 4096 Mar 2 23:54 gcc-4.7.1
As long as $LFS/sources is owned by lfs and the content of $LFS/sources is readable by user lfs, all is ok.
I personally run a chown lfs:root and chmod 440 on all packages and patches in $LFS/sources (in chapter 4.3 just before the su - lfs step). But I don't think that's actually needed.
I also see a lot of directories still present in $LFS/sources. Except for gcc and binutils that is probably ok (although the LFS team does mention removing them after building). The gcc and binutils dirs do concern me. aashayshah still needs to answer my question about that (post #20).
the other thing all packages are owned by user aashay aashay
Quote:
One question : Will it affect the lfs system if i compile and install perl first and then all other utilities like binutils , glibc , gcc in chapter 2 ( i.e. Temporary tools ) ???
Do you mean chapter 6?? you have gone past binutils etc in this chapter
One question : Will it affect the lfs system if i compile and install perl first and then all other utilities like binutils , glibc , gcc in chapter 2 ( i.e. Temporary tools ) ???
You need to follow the order in which the LFS book builds things!
PS: You still haven't clearly answered my second question, so just to make sure: You need to remove the extracted directory (and the build dir where appropriate) once you finish a package OR when you redo a package!!
As long as $LFS/sources is owned by lfs and the content of $LFS/sources is readable by user lfs, all is ok.
I personally run a chown lfs:root and chmod 440 on all packages and patches in $LFS/sources (in chapter 4.3 just before the su - lfs step). But I don't think that's actually needed.
I also see a lot of directories still present in $LFS/sources. Except for gcc and binutils that is probably ok (although the LFS team does mention removing them after building). The gcc and binutils dirs do concern me. aashayshah still needs to answer my question about that (post #20).
About your second question drunna , i tried deleting the the perl folder and again extracting it and compiling Still same errors occured . Bt according to spiky0011 i extracted it as a lfs user from command line and the compilation was successfull !!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.