Bug 170927
Summary: | libattr.a cannot be linked to anything with libtool | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Krzysio (Chris) Leszczynski <chris> |
Component: | attr | Assignee: | Thomas Woerner <twoerner> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | sct |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-05 15:42:57 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: |
Description
Krzysio (Chris) Leszczynski
2005-10-15 20:26:59 UTC
and I think a similar problem is happening with libacl. please consider fixing this soon. I am a KDE developer and I am having a hard time building code for the new KDE4 on FC4. (In reply to comment #0) > Description of problem: > > libtool replaces -all-static -lattr with /lib/libattr.a while libattr.a is in > /usr/lib/ > > > Version-Release number of selected component (if applicable): > libattr-devel-2.4.16-5 > libtool-1.5.16.multilib2-2 > > How reproducible: > Always > > Steps to Reproduce: > 1. create a trivial program, for instance > echo "int main(void){return 0;}" > trivial.c > > 2. Compile it > gcc -c trivial.c > > 3. Link it with libattr using libtool > libtool --mode=link gcc -o trivial trivial.o -all-static -lattr > > Actual results: > Libtool calls: > gcc -o trivial trivial.o -static /lib/libattr.a > > Expected results: > Libtool should call > gcc -o trivial trivial.o -static /usr/lib/libattr.a > > Additional info: > I think /usr/lib/libattr.la contains incorrect entry libdir=/lib From User-Agent: XML-RPC attr-2.4.24-1.FC4.1 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. |