On 6/11/2012 7:21 AM, Mike Young wrote:
root:/# find /tools -name "strict.pm <http://strict.pm>"
/tools/lib/per15/5.14.2/strict.pm <http://strict.pm>
root:/# find /tools -iname "*perl*"
/tools/bin/perl
/tools/lib/per15/5.14.2/TAP/Parser/SourceHandler/Perl.pm
/tools/lib/per15/5.14.2/Pod/Perldoc
/tools/lib/per15/5.14.2/Pod/Perldoc.pm
/tools/lib/per15/5.14.2/ExtUtils/Miniperl.pm
/tools/lib/per15/5.14.2/perl5db.t
/tools/lib/per15/5.14.2/PerlIO
/tools/lib/per15/5.14.2/unicore/README.perl
/tools/lib/per15/5.14.2/unicore/lib/Perl
/tools/lib/per15/5.14.2/unicore/lib/Perl/PerlSpac.pl
/tools/lib/per15/5.14.2/unicore/lib/Perl/PerlWord.pl
/tools/lib/per15/5.14.2/perl5db.pl <http://perl5db.pl>
/tools/lib/per15/5.14.2/PerlIO.pm
/tools/lib/per15/5.14.2/perl5db
/tools/lib/per15/5.14.2/Encode/PerlIO.pod
/tools/lib/per15/5.14.2/Perl
/tools/lib/per15/5.14.2/auto/Pod/Perldoc
/tools/lib/per15/5.14.2/auto/PerlIO
/tools/lib/per15/5.14.2/auto/Perl
/tools/include/asm-generic/bitsperlong.h
/tools/include/asm/bitsperlong.h
It seems that /tools/lib/perl5 is actually /tools/lib/per15 which I
can attribute down to myself. A simple mv /tools/include/per15
/tools/include/perl5 should fix this yes?
As for meaning to build for 64 or cross compiling. I'm currently
working on an x86_64 system so included all the commands for working
on such a system which I assume will also build for one?
Thanks
Mike
On Mon, Jun 11, 2012 at 12:53 PM, Yasser Zamani
<[email protected] <mailto:[email protected]>> wrote:
Date: Mon, 11 Jun 2012 12:35:59 +0100
From: [email protected]
<mailto:[email protected]>
To: [email protected]
<mailto:[email protected]>
Subject: [lfs-support] Book 7.1 Chapter 6.7 Linux API headers:
make headers_check
Hi all
This is my first lfs build, and it was going swimmingly until
I hit this little wall.
Unfortunately I am very much a newbie, so I have absolutely no
idea how to read these outputs (I'm just getting to grips with
what's actually going on!)
So, to the point. "make mrproper" went without any problems,
as did all sections prior to this.
Here are my actions and then the problem.
cd sources
tar -xf linux-3.2.6.tar.xz
cd linux-3.2.6
make mrproper
make headers_check
This gave the output of:
CHK include/linux/version.h
UPD include/linux/version.h
HOSTCC scripts/basic/fixdep
HOSTCC scripts/unifdef
INSTALL include/asm-generic (34 files)
Can't locate strict.pm <http://strict.pm/> in @INC (@INC
contains: /tools/lib/perl5/site_perl/5.14.2/x86_64-linux
/tools/lib/perl5/site_perl/5.14.2
/tools/lib/perl5/5.14.2/x86_64-linux /tools/lib/perl5/5.14.2
.) at scripts/headers_install.pl <http://headers_install.pl/>
line 19.
BEGIN failed--compilation aborted at
scripts/headers_install.pl <http://headers_install.pl/> line 19.
make[2]: ***
[/sources/linux-3.2.6/usr/include/asm-generic/.install] Error 2
make[1]: *** [asm-generic] Error 2
make: *** [headers_install] Error 2
Now Error 2, as I understand, is pretty generic, so at first I
though it's possibly not a real problem, but then I saw that
the compilation had aborted.
I removed the directory and re-extracted and started again,
getting exactly the same messages.
I haven't deviated from the book as far as I'm aware and my
host system matches the requirements.
Any ideas?
*The output tells that it could not find strict.pm
<http://strict.pm> in it's expected locations i.e.
/tools/lib/perl5/site_perl/5.14.2/x86_64-linux
/tools/lib/perl5/site_perl/5.14.2
/tools/lib/perl5/5.14.2/x86_64-linux /tools/lib/perl5/5.14.2.
<http://5.14.2.>*
*So please run following commands /_while you're chrooted into
$LFS _/and post back the result for us and also think about them
yourself:*
1.
*find /tools -iname "strict.pm <http://strict.pm>"*
2.
*find /tools -iname "*perl*"*
Thanks
Mike
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe:
See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Yes, a simple rename should work then. And yes, it will. Where trouble
would have come up is if you wanted to build a 32-bit system on a 64-bit
system or 64-bit capable system, as one must make sure it doesn't try to
compile for one in one package, then compile for the other on the next
package.
And a trick almost no-one starting out thinks of, especially for the sed
commands: use an HTML copy, and use the copy+paste method of inputting
the commands. It even works in the chroot.
Elly
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
