httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 45748] New: Issues With Hardcoded rpath On 64 bit Linux
Date Thu, 04 Sep 2008 21:06:56 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45748

           Summary: Issues With Hardcoded rpath On 64 bit Linux
           Product: Apache httpd-2
           Version: 2.2.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Build
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: thelvey@accelrys.com


We redistribute Apache httpd as part of our application so the installation
directory is never the same as the directory httpd is compiled for.
Additionally the functionality we provide requires that we can configure the
library search path at install time.
We just ran into a problem with several of our customers who installed our
software and found that they couldn't use the implemented database
functionality. After researching the issue we found that they had installed the
RedHat ODBC RPMs on their system and /usr/lib64 contained a library named
libodbc.so. We normally provide the DataDirect ODBC libraries as part of our
installation and set the LD_LIBRARY_PATH environment variable appropriately to
point to them. This has worked well with previous versions of httpd and seemed
to work when we did our testing, but we didn't have the RedHat ODBC libraries
installed on our test machines.
When we straced the server we found that it was always looking in the install
path /tmp/install/httpd-2.2.4/lib, then /usr/lib64 for everything first.
Looking at the strings in httpd we discovered the string
"/tmp/install/httpd-2.2.4/lib:/usr/lib64"
I spent about a day and a half fiddling with the config/libtool files to
finally get the hardcoded rpaths out of the compiled code, after compiling the
code without hardcoded rpaths everything seemed to work just fine and we could
again access the database functionality that was broken by them.
Would it be possible to either remove the hard coded rpath stuff from libtool
or at least provide a configuration option to turn it off? --disable-rpath
Hacking libtool is not very user friendly and there are a lot of places where
the hardcode_libdir_flag_spec shows up.

Thanks


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message