On Thu, Jun 05, 2003 at 04:01:27PM -0400, Jeff Trawick wrote:
seems like you could copy libgcc_s to Apache's lib directory... Apache's
bin/envvars file already updates LD_LIBRARY_PATH to include that directory
This works just fine. Allows us to make a self-contained Apache
package. The admin
We're upgrading from 2.0.44 to 2.0.46 and have noticed that the httpd
binary now seems to need libgcc_s.
# ldd /some/path/httpd
libaprutil-0.so.0 = /some/path/lib/libaprutil-0.so.0
libexpat.so.0 = /some/path/lib/libexpat.so.0
libapr-0.so.0 =
Build it with CFLAGS=-static-libgcc
On Thu, 2003-06-05 at 05:18, harald deppeler wrote:
We're upgrading from 2.0.44 to 2.0.46 and have noticed that the httpd
binary now seems to need libgcc_s.
# ldd /some/path/httpd
libaprutil-0.so.0 = /some/path/lib/libaprutil-0.so.0
harald deppeler wrote:
We're upgrading from 2.0.44 to 2.0.46 and have noticed that the httpd
binary now seems to need libgcc_s.
ugh
see also http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20447
# ldd /some/path/httpd
libgcc_s.so.1 = (file not found)
libgcc_s.so.1 =
Ok, I tried the CFLAGS=-static-libgcc trick, it didn't work for me.
Interpreting the compile log I gather that the c flag is carried through
from the configure stage up until to the final linking, however, it does
not achieve the desired result (see excerpt at the end of this mail). This
would
On Thu, 5 Jun 2003, harald deppeler wrote:
Ok, I tried the CFLAGS=-static-libgcc trick, it didn't work for me.
Did you verify that libtool passed the flag to the linker?
You can achieve that by removing --silent from the respective
Makefile.
- Sascha
