Summary: | apache-1.3.33 with +ssl in USE broken after upgrading gdbm to gdbm-1.8.3-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marek Wiecek <marek.wiecek> |
Component: | [OLD] Server | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | critical | CC: | fuzzyray, gentoo-bugs, matthias.foerste |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marek Wiecek
2004-11-15 04:32:05 UTC
It seems that the patch from : http://bugs.gentoo.org/attachment.cgi?id=37819 resolves the problem. Please confirm. i fixed this in the apache herd overlay some time ago Yes I know, but still, in apache-1.3.33.ebuild it isn't fixed. I have the same bug. apache-1.3.33. And mentioned above patch helped me. Please, someone fix this on cvs. Or there are some reasons not to do this? Same problem. Fixed with the patch at http://forums.gentoo.org/viewtopic.php?p=1928496#1928496 [adding -lgdbm_compat as in: LIBS="-lgdbm -lpthread -lgdbm_compat" - see discussion there]. This is with 1.3.33. I'd note that this showed up on a system which hadn't had Apache or mod_ssl updated for several versions. On another system which has been updated more often, this did not arise. So it may have something to do with how big a jump is made between versions of stuff. I jumped from version 1.3.31 to 1.3.33/mod_ssl 2.8.21 and had this problem. Reloaded the entire machine and started with 1.3.33/mod_ssl 2.8.21, and still same error. Using the fix from the forum seems to have worked, but won't be able to truly test until I'm local to the machine. Apache-1.3.33-r1 should fix this. It is currently hardmasked for testing. You can upgrade to the hardmasked version by following the insutructions in http://dev.gentoo.org/~vericgar/package-refresh.txt and http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html cannot confirm; LIBS="-lgdbm -lpthread -lgdbm_compat" did not work for me. could you try -lndbm please *** Bug 58624 has been marked as a duplicate of this bug. *** |