Now it's getting fun.
        Here's where I've gotten to, and am kind of stuck.
        Although I don't know how much your shared library linker
expertise goes, but I thought I'd ask.
        Either I'm way way off the mark or here's what's happening:

        When IHS parses httpd.conf it gets to the HTML:Embperl (we're
working with 1.3* here) and tries to load it and httpd blows up.
        I tracked it down to this: dXSARGS;
        Then I learned what XS is.
        You put MODULE = HTML::Embperl      PACKAGE = HTML::Embperl
PREFIX = embperl_
        in Embperl.xs and all sorts of stuff is generated by the
precompiler.
        So I dug. One macro leads to another and so on until I got to
this:
        SV **sp = PL_stack_sp;
        And that blows up with a segfault.
        PL_stack_sp is a pointer to a struct in libperl.so
        Can't even resolve the pointer. So I starting thinking linker.
        Then I started thinking that there wasn't much I can do about it
except go hunting around for  weird aix linker options. (Many a wise
developer has said bad things to me about the aix linker.)
        The only other thought I had was to see if it was them or me, so
I added a char *globalvar to Embperl.c and to mod_perl.c, added the
export, rebuilt both ran again.
        Embperl.c can find the one in Embperl.c but blows up the same
way when it tries to get the variable reference in mod_perl.c. Not good.
        I had one more thought: If I get a chance, which I probably
won't, I am going to try the whole shebang on 4.3.3 and see if that
helps. I can't see how whatever they did different between apache, and
IHS would cause the linker to go wonky like that. But I can see an OS
level change doing that.
        
        The other direction I went in for a little while, was just
trying mod_perl. It would seem that it loads okay, but it doesn't run
either.
        It dies here: perl_header_parser(0x20141a40), line 1017 in
"mod_perl.c"
        which is:    PERL_CALLBACK("PerlInitHandler",
cld->PerlInitHandler);
        Great. More macros.
        Haven't had a chance to chase this one down, but I'm betting
it's the same linker weirdness.
        So my next thing is to try 4.3.3 and see if that helps or causes
any change.

        I wonder if anybody has even certified IHS to run on 5.2, maybe
that's a problem in itself.

        If this rant has provoked any thought or insight, please, do
tell.


        



-----Original Message-----
From: HALL, SUSAN (SBCSI) 
Sent: Wednesday, May 31, 2006 11:54 AM
To: 'Gerald Richter'; MARK, STU (SBCSI)
Cc: embperl@perl.apache.org
Subject: RE: AIX/IHS and embperl build issues 



Gerald,
Thanks much for the typemap, the HTML-Embperl made ok with that.  We
installed and now we get a seg fault just running configtest as long as
the "PerlModule HTML::Embperl;" statement is in the httpd.conf.  We are
looking into that now.

Thanks for your help and I hope we will report final success soon.

Susan

-----Original Message-----
From: Gerald Richter [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 29, 2006 12:51 AM
To: HALL, SUSAN (SBCSI); MARK, STU (SBCSI)
Cc: embperl@perl.apache.org
Subject: RE: AIX/IHS and embperl build issues 


> 
> Here it is,

Seems like you hit a bug in Perl's xsubpp which converts the XS file to
the C file.

Try to replace the typemap file in the Embperl distribution with the
attached file. This hopefully should not hit the bug

Gerald



> Thanks, Susan
> 
> 
> 
> -----Original Message-----
> From: Gerald Richter [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 19, 2006 6:37 PM
> To: HALL, SUSAN (SBCSI); MARK, STU (SBCSI)
> Cc: embperl@perl.apache.org
> Subject: RE: AIX/IHS and embperl build issues
> 
> 
> > Syntax error: possible missing ';'
> > or ','?
> > "Embperl.c", line 299.1: 1506-277 (S) Syntax error: possible missing
> > ';' or ','?
> 
> Could you send me your Embperl.c ?
> 
> Gerald
> 
> 
>  
> ** Virus checked by BB-5000 Mailfilter **
> 
> 
> 
>  
> ** Virus checked by BB-5000 Mailfilter ** 
> !DSPAM:4471caf947842081013614!
> 


 
** Virus checked by BB-5000 Mailfilter ** 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to