[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: apache 2.0.45, mod_perl 2.0 (1.99-X), anyone?
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: apache 2.0.45, mod_perl 2.0 (1.99-X), anyone?
- From: Marcus Watts <mdw_(_at_)_umich_(_dot_)_edu>
- Date: Fri, 11 Apr 2003 03:00:12 -0400
Carl Brewer <carl_(_at_)_bl_(_dot_)_echidna_(_dot_)_id_(_dot_)_au> writes:
RRS text relocation at 0x17570 for "_Perl_hv_fetch"
Well, I know what this message means. You're taking code that wasn't
compiled to be relocatable and trying to bind it into a shared object
that has to be relocatable (pic, =position independent code). You
probably need to go back to your perl source and either figure out how
to make a "DynaLoader_pic.a", or a "DynaLoader.so", or how not to link
with this at all.
If you don't plan on loading any modules, you might be able to get away
without the line that has boot_DynaLoader in your source, but that does
put unnatural constraints on your perl scripts. perl links this
statically, probably because they figure it's bad kharma to try to
dynamically load the perl modules that loads perl modules. You could
just use -fPIC when building DynaLoader.a -- pic is just slightly
slower than absolute code, whereas absolute code is bad news in pic.
Alternatively, I suppose you could link your existing DynaLoader.a into
httpd. But really, using pic in DynaLoader.a is your best bet.
Visit your host, monkey.org