Hi,

actually, I double checked.. rebuild Apache2::Request from scratch after
removing every reference to existing A2::R.. Same error applies.
I never loaded the module into the httpd.conf though. I stuck to using it as
a replacement for CGI (but for mod_perl) :)

Hendrik

On Nov 11, 2007 7:46 PM, Fred Moyer <[EMAIL PROTECTED]> wrote:

> Hendrik Van Belleghem wrote:
> > This fixed the compilation.. but when I loaded it in my code, it spit
> > out the following message in my logs:
> >
> > dyld: lazy symbol binding failed: Symbol not found:
> _apreq_handle_apache2
>
> I'm going to take a guess here and say that you have more than one
> version of libapreq installed.
>
> or... are you sure that you have LoadModule apreq_module mod_apreq2.so
> pointing to the correct version of libapreq?
>
>
> >   Referenced from: /Library/Perl/5.8.8/darwin
> > -thread-multi-2level/auto/APR/Request/Apache2/Apache2.bundle
> >   Expected in: dynamic lookup
> >
> > dyld: Symbol not found: _apreq_handle_apache2
> >   Referenced from:
> >
> /Library/Perl/5.8.8/darwin-thread-multi-2level/auto/APR/Request/Apache2/Apache2.bundle
> >   Expected in: dynamic lookup
> >
> > Anyone any suggestions on how to fix this?
> >
> > Hendrik
> >
> >
> > On Nov 11, 2007 6:12 PM, Laurent MARTIN <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> >
> >     Hi there!
> >
> >     I'm trying to install libapreq2 under my newly installed Mac OS X
> >     10.5 on a MacBook Pro (Core Duo 2, SantaRosa), but something must be
> >     wrong in what I'm doing as Apache refuses to launch as soon as I add
> >     the following to the httpd.conf file:
> >     LoadModule apreq_module libexec/apache2/mod_apreq2.so
> >     Below is the message I get in the console:
> >     httpd: Syntax error on line 509 of /private/etc/apache2/httpd.conf:
> >     Cannot load /usr/libexec/apache2/mod_apreq2.so into server:
> >     dlopen(/usr/libexec/apache2/mod_apreq2.so, 10): no suitable image
> >     found.  Did find:\n\t/usr/libexec/apache2/mod_apreq2.so: mach-o, but
> >     wrong architecture
> >
> >     FYI, I'm using the default softwares provided with Leopard: Apache
> >     2.2.6 & mod_perl 2.0.2 & Perl 5.8.8.
> >
> >     What I'm typing to install libapreq2:
> >     % perl Makefile.PL --with-apache2-apxs=/usr/sbin/apxs
> >     % make
> >     % sudo make install
> >
> >     I've noticed the following message while compiling (make):
> >     ld: warning in
> >     /Users/laurent/Downloads/libapreq2-2.08
> /library/.libs/libapreq2.dylib,
> >     file is not of required architecture
> >
> >     If it can help, here is what I get when I apply the "file" command
> >     on this .dylib file:
> >     /Users/laurent/Downloads/libapreq2-2.08
> /library/.libs/libapreq2.dylib:
> >     Mach-O dynamically linked shared library i386
> >     After having installed (sudo make install), here is what I get when
> >     I apply the "file" command on the newly created and
> >     installed /usr/libexec/apache2/mod_apreq2.so file:
> >     /usr/libexec/apache2/mod_apreq2.so: Mach-O bundle i386
> >     Is this normal? Below is what I get for example for the mod_perl.so
> >     file:
> >     mod_perl.so: Mach-O universal binary with 4 architectures
> >     mod_perl.so (for architecture ppc7400): Mach-O bundle ppc
> >     mod_perl.so (for architecture ppc64): Mach-O 64-bit bundle ppc64
> >     mod_perl.so (for architecture i386): Mach-O bundle i386
> >     mod_perl.so (for architecture x86_64): Mach-O 64-bit bundle x86_64
> >     Shouldn't I get the same for all .so file? Shouldn't mod_apreq2.so
> >      be compiled as universal binary too?
> >
> >     Any idea? Thank you very much in advance!
> >
> >     --
> >     *Laurent*, Nantes (FR) -  *http://blog.lmartin.fr*
> >     <http://blog.lmartin.fr/>
> >     /Apple MacBook Pro 15"/
> >     /Nokia Internet Tablet N800/
> >     /Palm Treo 650 (unlocked GSM)/
> >
> >
> >
> >
> > --
> > Hendrik Van Belleghem
> > Spine - The backbone for your website - http://spine.sf.net
>
>


-- 
Hendrik Van Belleghem
Spine - The backbone for your website - http://spine.sf.net

Reply via email to