Produits Entr'ouvert » Lasso

Sorry, this is a mistake.

The compilation log is not useful. I think you will need to obtain a proper traceback and maybe to print the problematic reference if you want to advance on this bug. There is not a lot of commits on the perl binding tree, maybe you could pinpoint which commit introduced this regression by doing som git-bisecting between the 2.3.6 and 2.4.0 release.

In fact, I do reproduce the bug in 2.3.6 version, compiled on debian wheezy 32bits.

Not a CODE reference at /usr/share/perl/5.14/XSLoader.pm line 95.
END failed--call queue aborted at /usr/local/lib/perl/5.14.2/Lasso.pm line 95.

Si it is harder to point where the bug is...Do you know how I could easily get the traceback or the problematic reference ?

So maybe the problem do not come from a change in Lasso but a change in Perl...

Hi Benjamin,

seems the Perl version is the same for Wheezy 32bits and Wheezy 64bits: https://packages.debian.org/wheezy/perl

Could this not be a problem in the Lasso XS code?

As LemonLDAP::NG is only the user of the Perl binding, you cannot expect any outside experience. What's the last version of lasso whose Perl binding worked on a Debian platform and what version of Debian was this plaftorm using ?

That could help you for determining what changed on Perl side that broke the XS code which did not change in the meantime (last change to the XS generator is from 2010).

I don't know if LemonLDAP::NG is the only project that use the Perl binding. A recent message in the mailing list shows that someone else would like to give it a try. Anyway, I hope you will still support it.

I have a working Lasso perl binding on a Debian Squeeze 32 bits, and David has a working configuraiton on Wheezy 64 bits. My Ubuntu 12.04 (wheezy/sid) 64 bits Lasso installation works also very well.

I am not familiar with the XS code, I am not sure to be able to debug it.

Clément Oudot a écrit :

I don't know if LemonLDAP::NG is the only project that use the Perl binding. A recent message in the mailing list shows that someone else would like to give it a try. Anyway, I hope you will still support it.

We won't. It's a free software project, user must support (not only code, documentation, packaging or really clean bug report are included are great contributions) code they are using or it's gonna rotte. We do work on what we need; if nobody provide a patch to fix perl lasso binding on Debian in the future, the package will someday disapear, that's how it works. There was a C# binding and windows compilation support a long time ago, now it's gone.

I am not familiar with the XS code, I am not sure to be able to debug it.

I'm not familiar with it anymore; last time I looked at it was at least two years ago and I never use Perl myself. If I could provide easily any direct insight for fixing this bug I would. So do some detailed analysis of the problem (I haven't seen any until now) or buy support but do not expect anything more than guidance from me based on what you report.

I'm petty sad to read that. I know what free software is, and what it cost to maintain it.

We will try to do our best to dig into the bug anyway.

Clément Oudot a écrit :

I'm petty sad to read that. I know what free software is, and what it cost to maintain it.

Don't be, weather is great today in Paris, I hope it is too in Lyon.

We will try to do our best to dig into the bug anyway.

Great. I'll read your reports and give insight if I can.