Re: [Swig-user] undefined symbol: PL_sv_undef

[Barry A. <tit...@gm...>]

I will try it and let you guys know.

"I can't tell you the details of how Perl or SWIG does what it does, and
would rather remain ignorant."

I'm with you there man. :)

On Tue, Jun 17, 2008 at 4:34 PM, Josh Cherry <jc...@nc...>
wrote:

>
>
> On Tue, 17 Jun 2008, Barry Andrews wrote:
>
>  Thanks Josh. Makes sense. But headers are the same whether you have
>> multithreaded Perl or not, i.e. there's not separate headers for each.
>> Directives are controlling this.
>>
>
> Have you diff'ed all of the headers to determine that they're identical?
>
>  As far as SWIG goes, do you know how it knows which Perl you have?
>>
>
> It doesn't.
>
>  I am wondering how does it know to generate PL_sv_undef versus something
>> else?
>>
>
> It doesn't.  It has preprocessor stuff to do the right thing.  I've only
> glanced at the code.
>
> I can only offer the practical advice to build against an mt Perl
> installation for use with mt Perl and non-mt Perl for use with non-mt Perl,
> using the same SWIG-generated code.  I can't tell you the details of how
> Perl or SWIG does what it does, and would rather remain ignorant.
>
> Josh
>
>