At 10:03 PM 05/20/02 +0100, Nick Ing-Simmons wrote:
>It works on linux/solaris and probably elsewhere with modern C++ 
>systems.

What "it" are you referring to?  My module?

>Anything which mixes C++, exceptions and dynamic loading is not 
>going to be as portable as perl (which is just ANSI C).

What's weird is that my two linux systems are very similar.  I might expect
it to not work on a different platform, but not on two different linux
systems.

My SuSE 6.2:
  Perl 5.6.0 built from source, gcc version 2.95.3 20010315 (release)

My Debian Woody is 
  Perl 5.6.1 debian package, gcc version 2.95.4 20011002 (Debian prerelease)
  GNU gdb 2002-04-01-cvs

I installed the aspell/pspell code from source on all machines.

So it's a bit odd that it works on my SuSE machine but aborts on the
Debian.  Not a lot of difference.  Could be a missing library, I suppose,
but I don't know how to detect this.  (My use of) gdb, strace and ltrace
have not helped.

And I just don't know what to thing about PERL_DL_NONLAZY.  I thought all
that did was set a flag (RTLD_NOW) on dlopen calls made by perl.  So it
seems odd that would effect the c++ code at all.

I just now build Perl 5.7.3 on Debain and it's exactly the same problem.

This works:

PERL_DL_NONLAZY=0 /home/moseley/perl/ithread/bin/perl5.7.3 -I'blib/lib'
-I'blib/arch' t/test.t 

This does not (e.g. "Aborted")

PERL_DL_NONLAZY=1 /home/moseley/perl/ithread/bin/perl5.7.3 -I'blib/lib'
-I'blib/arch' t/test.t 





-- 
Bill Moseley
mailto:[EMAIL PROTECTED]

Reply via email to