in reply to PERL_DL_NONLAZY and make test failure

Well, the easiest thing to do is to load up the module by hand and see what it yells about.
perl -Ilib/blib -Ilib/arch -MText::Pspell
and look through the output. It all should be there.

Whether or not the unresolved symbols will be a problem for you is another matter entirely. They are a problem, as there's code in the library that will crash and burn when run, but you might not use that stuff.

Libraries that don't completely resolve isn't unusual, unfortunately. Late binding of library code gives an adequate speed boost, but it tends to encourage sloppy building since you don't always find your problems until runtime. (Usually in error handling functions, of course, since what else would use routines only really occasionally? That and it's the most inconvenient thing, so it's liklely to happen)

Replies are listed 'Best First'.
Re: Re: PERL_DL_NONLAZY and make test failure
by Anonymous Monk on May 13, 2002 at 22:33 UTC
    Well, the easiest thing to do is to load up the module by hand and see what it yells about.

    perl -Ilib/blib -Ilib/arch -MText::Pspell

    That doesn't complain about anything. But that's not preloading with PERL_DL_NONLAZY, although PERL_DL_NONLAZY=1 doesn't change anything.

    I'm not really looking for a way around the problem, but rather how to debug -- specifically how to find out what is unresolved. I guess it's not exactly a "perl" problem, but a lack of good unix debugging skills on my part. Thanks,