Bug#742522: liblasso-perl: Not a CODE reference when using perl binding for Lasso

2014-03-31 Thread David Coutadeur
Le 28/03/2014 16:47, Frederic Peters a écrit : Niko Tyni wrote: this is usually a result of compiling perl XS extensions without $Config{ccflags}, currently resulting in binary incompatibility on 32-bit architectures. See #628522. I see bindings/perl/Makefile.am explicitly overrides CCFLAGS wit

Bug#742522: Re: Bug#742522: liblasso-perl: Not a CODE reference when using perl binding for Lasso

2014-03-25 Thread David Coutadeur
After some more investigation, I found out that: - $xs is really a code reference - it does not contain any code... Or the code is not correctly deparsed Here is the Dynaloader modified code: use Data::Dumper; $Data::Dumper::Deparse = 1; print Dumper($xs); print "ref: ".ref($xs)

Bug#742522: Re: Bug#742522: liblasso-perl: Not a CODE reference when using perl binding for Lasso

2014-03-25 Thread David Coutadeur
After some more investigation, I found out that: - $xs is really a code reference - it does not contain any code... Or the code is not correctly deparsed Here is the Dynaloader modified code: use Data::Dumper; $Data::Dumper::Deparse = 1; print Dumper($xs); print "ref: ".ref($xs)

Bug#742522: liblasso-perl: Not a CODE reference when using perl binding for Lasso

2014-03-24 Thread David Coutadeur
Package: liblasso-perl Version: 2.3.6-2 Severity: grave Justification: renders package unusable When using perl Lasso binding on Debian wheezy 32bits, I get this error message: PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/Lasso.