I really want to create a re-locatable package.
Using 'objdump -p httpd' it shows that the run path RPATH includes
/usr/lib64
RPATH /home/developer/opt/myapp/apr-util:
/usr/lib64:
/home/developer/opt/myapp/apr
Is there any way to avoid /usr/lib64 to be included in RPATH?
Is
Hi,
I'm still trying to find a solution.
Is there any way to link the APR statically?
Thanks
-Jorge
-Original Message-
From: Jorge Medina [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 4:49 PM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] How do I tell Apache
Did you specify the path with ./configure?
--with-apr=PATH prefix for installed APR or the full path to
apr-config
--with-apr-util=PATHprefix for installed APU or the full path to
apu-config
At 08:09 AM 9/17/2008, Jorge Medina wrote:
Hi,
I'm still trying to find a
Yes, but the original path to the APR and APR-util is not the same as in
the deployment machine.
I specify the paths
--with-apr=/home/developer/opt/myapp/apr
--with-apr-util=/home/developer/opt/myapp/apr-util
But when my app gets deployed (just the binaries), the paths may
change to something
Can you create your production layout on your build machine and do it that
way? We do something like this by having a standard layout on our
production servers so we can build the binaries on our build machine and
then transfer them over to the production boxes. We use stow to make
I also ran
# apachectl -V
And I get that other versions of the APR and APR-Util are getting
loaded, not the versions I compiled against.
LD_LIBRARY_PATH is set to
/opt/myapp/apache/lib:/opt/myapp/apr/lib:/opt/myapp/apr-util/lib:
Server version: Apache/2.2.8 (Unix)
Server built: Sep 16 2008
