On Sat, May 31, 2008 at 4:41 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> On Fri, 30 May 2008, Andy Dougherty wrote:
>> On Sat, 31 May 2008, Brendan O'Dea wrote:
>> > Not really. Adding a version into the path simply changes the failure
>> > from an issue loading the .so (module is unusable) to one where the
>> > module is not found at all (module is unusable).
> [...]
> That's wrong. The "use Locale::Gettext" is protected by eval {} and
> update-alternatives works well when the eval fails... as it subsitutes
> gettext() with a simple sub return { [EMAIL PROTECTED] }.
> That's why the initial request was to disable lazy symbol loading inside
> eval.
I was aware of the optional loading of Locale::gettext, but don't
believe that changing the dlopen behaviour upstream is the right
solution.
This is a Debian-specific problem, and moreover one which occurs in a
very narrow set of circumstances: programs/modules which
opportunistically load a module (hence circumventing the dependency
model) across upgrades to perl which change the binary ABI (which are
rare).
Modifying update-alternatives to set $ENV{PERL_DL_NONLAZY} would
appear to be the most appropriate solution here.
--bod
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
