Here is the contents of libpcre.pc from /usr/lib/pkgconfig

# Package Information for pkg-config

prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib <== THE PROBLEM MAY BE HERE SHOULDN'T IT BE libdir=/lib
includedir=${prefix}/include

Name: libpcre
Description: PCRE - Perl compatible regular expressions C library
Version: 6.6
Libs: -L${libdir} -lpcre
Cflags: -I${includedir}

Since cherokee uses pkgconfig to verify paths, the pcre files are not located in as libpcre.pc states, /usr/lib, but /lib.  Before recompiling pcre to put .so and .a files in /lib, cherokee found the .a files in /usr/lib but failed to find the .so files in /usr/lib and failed.

Since I reinstalled the files in /lib, but not modifying the libpcre.pc file, cherokee localted the files in /lib (.a and .so), thus ignoring the libpcre.pc settings for libs.

So either the pcre PKGBUILD is changed to force the libraries to be installed to /lib, which would fix the libpcre.pc, or use what I suggested and possibly sed the $startdir/pkg/usr/lib/pkgconfig/libpcre.pc file to reflect the proper libdir.

Does this explain it any better


On 5/12/06, rod smith <[EMAIL PROTECTED]> wrote:
The PKGBUILD I am using is from cvsup, /var/abs/base/pcre updated as of today, just before trying to build cherokee again.  The .a files are not moved and the PKGCONFIG file is not updated to reflect the new location.

Also I am not the only one with the problem.  WillySilly who is the maintainer was having the same problem compiling cherokee-0.4.x-0.5.3.  

This is a work-around that I found and am in the process of trying to make it a little cleaner/easier than having to rebuild pcre so the .a and pkgconfig info is redone.



 
On 5/12/06, Tobias Kieslich < [EMAIL PROTECTED]> wrote:
On Fri, May 12, 2006 at 17:26:48 +0200, Jan de Groot wrote:
> Now my question is... why does cherokee take the static libraries while
> shared ones are available? Do you tell it to do so or does it take them
> by default?
> As pcre is in the base (grep needs it), shared linking should be
> considered.

Now, in my opinion something is weird with pcre. Its shared objects are
located in /lib/libpcre* while it has static .a files in
/usr/lib/libpcre*.a
The build he describes is prolly the the PKGBUILD from community which
sports an explicit --disable-static iirc.
So something is messing with the pathes, and I'm not 100% positive it's
cherokees fault.

        -tobbi

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch


_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to