Try this and see if it works. I think it works for me (i just was working on
this yesterday).
I downloaded and built PCRE separately (8.35). I'm building on both Linux and
Solaris at this point.
./configure \
--disable-cpp \
--disable-shared \
--prefix=$LOCALDIR/$PCRE_VER
make
make install
(I have --disable-cpp as a suggestion I found for building on Solaris. You may
not need it).
Then when configuring Apache had this as part of the configure command
.
.
.
--enable-pcre=static \
--with-pcre=$LOCALDIR/$PCRE_VER \
.
.
.
Hope that works for you.
----- Original Message -----
From: [email protected]
To: [email protected]
Sent: Friday, May 23, 2014 10:56:40 AM GMT -05:00 US/Canada Eastern
Subject: [users@httpd] How to link pcre statically into Apache 2.4.9?
At work we compile Apache ourselves with some custom modules. I have been
asked to upgrade from Apache 2.2 to Apache 2.4. The build script mostly
works but we would like to continue to link pcre in statically and I am
struggling to find the right combination of switches to configure.
The decoupling of pcre is causing me problems. Ideally I would like to be
able to treat pcre as apr and apr-util and build it in the Apache tree as
in 2.2. Having failed to do that I would now like to link pcre statically.
I have tried the following two with no joy:
--enable-pcre=static
--enable-mods-static="pcre"
but it is still linked dynamically:
ldd .libs/httpd | grep pcre
libpcre.so.1 => lib/libpcre.so.1
I realise that this is not the preferred direction but would like to link
it statically for the time being. I will keep plugging away but if anyone
still does this what am I missing?
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
