perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Kaluza <jkal...@redhat.com>
Subject Re: [httpd24 branch] merge with trunk?
Date Fri, 12 Jul 2013 04:29:12 GMT

----- Original Message -----
> Jan Kaluža wrote on 2013-07-11:
> > On 07/11/2013 10:41 AM, Steve Hay wrote:
> >> Jan Kaluža wrote on 2013-07-11:
> >>> On 07/11/2013 01:17 AM, Steve Hay wrote:
> >>>> The first problem was "Warning (mostly harmless): No library found
> >>>> for -laprutil-1" appearing from Makefile.PL between
> >>>> ModPerl::WrapXS and APR (presumably it applies to the latter),
> >>>> which I've ignored for now but will probably come back to bite me
> >>>> later. No other such issues are reported, and all the libraries
> >>>> (apr-1.lib, aprutil-1.lib, libapr-1.lib, libapriconv-1.lib,
> >>>> libaprutil-1.lib, libhttpd.lib, mod_dav.lib and xml.lib) are
> >>>> together in C:\Apache24\lib, so I'm not sure what the problem is there
> >>>> yet.
> >>> 
> >>> After thinking about that for a bit and checking all my patches
> >>> I've found out there's the same problem on Linux. I have overcame
> >>> that with quite hardcoded way last year when trying to get it work:
> >>> 
> >>> http://jkaluza.fedorapeople.org/mod_perl/0020-Link-APR.so-against-
> >>> libaprutil-1.patch
> >>> 
> >>> Something like that is probably needed on Windows too. Proper way
> >>> would be to fix Apache2::Build to include this library, but I was not
> >>> able to achieve that last year if I remember well.
> >>> 
> >> 
> >> I see that patch is in the httpd24 branch so it is already being
> >> done
> > on Windows just like any other OS, but the problem is that the path to
> > the library in question isn't known.
> >> 
> >> In my build $libs is
> >> 
> >> -LD:\temp\mp2\MODPER~1\blib\arch\auto\LIBAPR~1 -laprext -laprutil-1
> >> 
> >> and libaprutil-l.lib is in D:\temp\mp2\apache\lib. If I manually add
> > -LD:\temp\mp2\apache\lib into $libs then it builds fine but I'm
> > struggling to automate that at the moment.
> > 
> > Right, I had the same problem with automation and I decided to
> > hardcode it for Linux :(.
> > 
> 
> Where/how have you hard-coded the *path* to that library, though? I only see
> the library *name* hard-coded:

I don't, on Linux compiler has predefined paths where to find the libraries, so if the library
is in that default path, it will be found.

Regards,
Jan Kaluza

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message