Yes. But I build the APR and the APU libraries myself (and include them in my
tar.gz file).
Since I also enable SSL, I also build OpenSSL and pass the path to it at build
time with -with-ssl and with LD_LIBRARY_PATH at runtime.
export CPPFLAGS="-m64 -O3"
export CXXFLAGS="-m64 -O3"
export CFLAGS="-m64 -O3"
configure \
--with-ldap \
--quiet \
--srcdir=${HTTPD_ROOT} \
--with-port=80 \
--enable-mods-shared="all headers ssl ldap authnz_ldap info echo mime proxy
proxy_ajp proxy_balancer" \
--prefix=/home/user/opt/apache \
--with-apr=${APR_DIR} \
--with-apr-util=${APU_DIR} \
--with-expat=builtin \
--with-mpm=worker \
--with-ssl=${OPENSSL_TARGET_DIR} \
--enable-lib64
________________________________
From: Aruna Gummalla [mailto:[email protected]]
Sent: Wednesday, November 18, 2009 3:29 PM
To: [email protected]
Subject: RE: [us...@httpd] Apache build
Thanks Jorge.
Is it possible to build for x86-64 machine?
I am trying to build with --host=x86_64-linux-gnu --enable-lib64=yes
It builds but when I look at the modules file mod_ssl.so. They are all 32 bit
only.
What could be the mistake that I am doing.
Please let me know.
Thanks & Regards,
Aruna.
--- On Thu, 11/19/09, Jorge Medina <[email protected]> wrote:
From: Jorge Medina <[email protected]>
Subject: RE: [us...@httpd] Apache build
To: "[email protected]" <[email protected]>
Date: Thursday, November 19, 2009, 1:49 AM
It is doable. I compile my own apache and provide it as a tar.gz file bundled
with other set of scripts.
If the paths on the target machine do not match the paths on your build
machine, then you will need to define LD_LIBRARY_PATH
________________________________
From: Aruna Gummalla [mailto:[email protected]]
Sent: Wednesday, November 18, 2009 3:11 PM
To: [email protected]
Subject: [us...@httpd] Apache build
Hi,
I want to build httpd server and install on some other machine with my own
build scripts.
Does it hard codes any paths internally?
Thanks & Regards,
Aruna.
