Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 75639
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 75636
Assigned To: Gentoo Toolchain Maintainers <toolchain@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dan Armak (RETIRED) <danarmak@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 75639 depends on: Show dependency tree
Bug 75639 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-12-25 11:29 0000 
With the new binutils, libiberty.a isn't in /usr/lib anymore. kmtrace needs
to link against it. How can I find out the current binutils profile's library dir
from an ebuild? The output of binutils-config -c isn't very helpful, it'd need
some mangling and kmtrace would need to know about the /usr/lib/binutils dir
structure.

kmtrace is a kde malloc debugger that uses glibc's mtrace. It's currently part of
the kde-base/kdesdk ebuild.

------- Comment #1 From SpanKY 2004-12-26 00:23:27 0000 ------- 

*** This bug has been marked as a duplicate of 75636 ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug