Ken Moffat wrote:
> On Wed, Aug 15, 2012 at 04:56:06PM +0100, Ken Moffat wrote:
>>   For the moment, please don't treat this as a priority.  I've been
>> distracted by other things today and am nowhere near confirming that
>> it is indeed a perl-5.16 problem.  If it isn't caused by perl-5.16,
>> then fixing the perl is not the right answer.
>>
>>   OTOH, if anyone is building 32-bit and can keep the glibc source
>> and build directories around, testing a change to the perl script
>> should only take a few seconds.  Oddly, I had to run it from within
>> the *source* directory.  If I do blame the perl version [ plausible,
>> a lot of "baggage" was dropped in 5.16 ], I'll produce instructions
>> for changing the file and for how to run it.
>>
>   Bad news, I get the same regex error with perl-5.14.2.

I don't think it's a perl issue.

>   I think that means our build process is no longer adequate for this
> version of glibc.  So, it removes much of the purpose in running the
> testsuites.  Perhaps it's a similar issue to Bryan's question about
> why packages are now using gnulib instead of our headers (the gets
> seds).  At the moment, I'm out of my depth.

How long have these packages been using their own version of gnulib?  As 
a developer, I can see why they might want to have control over that 
package by including their own package and building it into their own 
packages/libraries.

>   In passing, I was wrong to say it's a simple thing to test : a
> large amount of glibc gets installed before test-installation.pl is
> run, and from a situation where nothing of glibc has been installed
> I haven't found a shortcut to only installing the minimum necessary
> to run the script.  I suppose that isn't surprising, it runs as the
> *last* part of the install.

I'm building glibc again now with the test-installation.pl script left 
in.  I'll investigate more and let you know if I find something new.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to