Bug 41863
| Summary: | ldconfig -v returns error | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Curtis Doty <curtis> |
| Component: | libstdc++ | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-05-22 17:45:12 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: | |||
It is not error, it is a warning and only printed with -v. If you want ldconfig verbose, then it is really verbose. I don't consider this a bug at all. |
Reproduce: # ldconfig -v 1>/dev/null ldconfig: Path `/usr/lib' given more than once Observation: libstdc++-2.96-81 postinstall script does echo /usr/lib >>/etc/ld.so.conf but I'm guessing that path is already hard coded into glibc? Hack: remove /usr/lib from /etc/ld.so.conf Is that a safe thing to do?