On Mon, Jun 16, 2014 at 09:22:30PM +0200, Stefano Stoduto wrote: > On 16 June 2014 16:49, Ken Moffat <[email protected]> wrote: > > > On Mon, Jun 16, 2014 at 10:03:52AM +0200, Stefano Stoduto wrote: > > > > It looks as if @INC is the problem. I don't have a version of > > /tools handy, but I can see that perl is configured for /usr/local > > which is its default location. Fortunately, it is not installed > > there because the lfs user cannot write there, and anyway we > > installed it by copying to /tools. > > > > So, something seems to be wrong in the command > > sh Configure -des -Dprefix=/tools > > > > After running that command, a file config.sh is created. I've just > > done that andin my case there are some lines (starting at line 891 > > in my case) - > > > > prefix='/tools' > > prefixexp='/tools' > > privlib='/tools/lib/perl5/5.18.2' > > privlibexp='/tools/lib/perl5/5.18.2' > > > > I assume you got different values. If you no longer have that > > file, please try again (just the configure command, then check the > > file). > > > I still got the config.sh file from the last compilation. The lines you > mentioned are at line 891 in my case too, they are: > > prefix='/usr/local' > prefixexp='/usr/local' > privlib='/usr/local/lib/perl5/5.18.2' > privlibexp='/usr/local/lib/perl5/5.18.2' > > I suppose that this indicates that I am using the host perl installation. > So what should I do?
No, it means that you configured perl for /usr/local (i.e. something was wrong in the configure command, or it did not work as we expect) but installed it in /tools. Because we do an "install by copying" for perl in chapter 5, that can happen. The question is, why did it get configured for /usr/local when you appear to be correctly copying the commands. At the moment, I think the following are the two most-likely alternatives: (a) you did not key the command in full, or mistyped the -Dprefix part. If you have still have the command in the LFS user's history, you can check that. If you do not have that information, try it again and see if the results in config.sh change. (b) your shell is not working as we expect. If '(a)' did not solve the problem, please try: (b1) /usr/bin/bash Configure -des -Dprefix=/tools and look to see if that gives any difference in that part of config.sh (b2) /tools/bin/bash Configure -des -Dprefix=/tools and again look at those lines in config.sh. For both of those, the path to bash is required so that we know which version is being used. At the moment, I am trying to understand why the command appears to be doing the wrong thing. If you have dash (the host's original /bin/sh) you could also try (b3) dash Configure -des -Dprefix=/tools to get more possible evidence. It is, of course, possible that something else entirely is causing the problem on this particular host distro. As you originally noted, this is not the first time the error has happened. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
