Bug 146846
Summary: | httpd won't start. Cannot load /etc/httpd/modules/libphp4.so into server: /usr/lib/libcurl.so.3: undefined symbol: tld_strerror | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Roberts <awroberts> | ||||
Component: | curl | Assignee: | Eido Inoue <havill> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-02-02 14:03:47 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Alex Roberts
2005-02-02 01:16:26 UTC
Works fine for me. Did you --nodeps an upgrade? Was this system upgraded from Fedora Core 2? What's the output of: # ldd /usr/lib/libcurl.so.3 # rpm -q libidn # ls -l /usr/lib/libidn.so.* # ldd /usr/lib/libidn.so.* Created attachment 110547 [details]
libcurl, libidn debug output
This was a fresh install of Fedora Core 3. I did the update of curl and curl-devel w/ 'yum -y update curl curl-devel'. I noticed on a couple of other FC3 systems that I cannot recreate the bug. They all have the distinction of not having been rebooted. I'm not sure if that makes a difference, but it's the one main difference I can think of between those systems and the problem system. I saw that libidn and libidn-devel were not the same version as the other systems. Not sure how that happened since I only use yum to update them and they're all pulling from the same repository. Anywho, I updated libidn and libidn-devel using rpm instead of yum and all seems to work now. I'll mark this as 'Not a bug' and note that the problem is between the keyboard and chair. |