On Wed, 19 Oct 2005, Ken Moffat wrote:
For the temporary tools, I'm guessing we could just build a 32-bit perl
(assuming any 64-bit testsuites will NOT produce perl modules).
Progress update:
Using the 20051017 glibc snapshot and ONLY a 32-bit perl in test-tools,
the 64-bit glibc
On Wed, 2005-10-19 at 02:07 +0100, Ken Moffat wrote:
Hi,
it appears to me that the perl installations in a multilib build are
broken. First, in the temporary tools we end up with a /tools/bin/perl
which thinks it is a 32-bit program because it uses the Config.pm from
the 32-bit
On Thu, 2005-10-20 at 11:55 +1000, Ryan Oliver wrote:
SNIP
updated patch attached, should be fine for MIPS n32 too ( ie lib32 )
[R]
--- perl-5.8.7/Configure-ORIG 2005-10-20 11:49:47.571389008 +1000
+++ perl-5.8.7/Configure 2005-10-20 12:30:35.571236464 +1000
@@ -5930,6 +5930,8 @@
: The default
Ken,
I will update cross-lfs with this information. Working with Ryan on
it as we speak.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
In some non-list traffic, there has been some discussion of UTF-8 for
{,B}LFS. I'm posting this discussion to the wider community for comments.
The question is: should {,B}LFS support UTF-8? If so, who will be
responsible for the UTF-8 specific portions of the books and how should
the material
