develooper Front page | perl.perl5.porters | Postings from May 2008

Re: Blead smoke failure: Can't load *.so

Thread Previous
From:
Andy Dougherty
Date:
May 16, 2008 10:08
Subject:
Re: Blead smoke failure: Can't load *.so
Message ID:
Pine.LNX.4.64.0805161304560.9993@fractal.phys.lafayette.edu
On Sun, 3 Feb 2008, Andy Dougherty wrote:

> On Sun, 3 Feb 2008, Moritz Lenz wrote:
> 
> > Andrew Dougherty wrote:
> > > On Fri, 1 Feb 2008, Nicholas Clark wrote:
> > > 
> > >> On Tue, Jan 29, 2008 at 02:53:34PM +0100, Moritz Lenz wrote:
> > >> > I compiled a fresh blead copy with

> > >> > In the test output there are many errors like this:
> > >> > 
> > >> > lib/Log/Message/Simple/t/01_use...............................#   Failed
> > >> > test 'use Log::Message::Simple;'
> > >> > #   at ../lib/Log/Message/Simple/t/01_use.t line 6.
> > >> > #     Tried to use 'Log::Message::Simple'.
> > >> > #     Error:  Can't load '../lib/auto/Data/Dumper/Dumper.so' for module
> > >> > Data::Dumper: ../lib/auto/Data/Dumper/Dumper.so: undefined symbol:
> > >> > __stack_chk_fail_local at ../lib/XSLoader.pm line 64.
> > >> > #  at ../lib/Data/Dumper.pm line 36

> I guess Configure's test of whether or not it's safe to add 
> -fstack-protector is insufficiently robust, but it's not immediately 
> obvious to me what to fix.  Offhand, I wonder if we need to add 
> -fstack-protector to lddlflags or cccdlflags or some other dynamic-loading 
> related variable.  It will take some checking.

Yes, that was it.  We did indeed need to add -fstack-protector to 
lddlflags.  See [perl #54120] for a metaconfig patch.  As this will 
require a regen of Configure, it won't apply cleanly to bleadperl as is, 
but should eventually get fixed.

Thanks for the report.  Sorry it took so long to fix it.

-- 
    Andy Dougherty		doughera@lafayette.edu

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About