Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 270438 - dev-utils/ltrace fails on build
Summary: dev-utils/ltrace fails on build
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: High minor
Assignee: Development Tools Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-19 14:56 UTC by Otheus
Modified: 2012-10-22 17:57 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch to resolve problem (ltrace-summary.patch,536 bytes, patch)
2009-05-19 15:00 UTC, Otheus
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Otheus 2009-05-19 14:56:20 UTC
fails on build if if libiberty is not installed. Fails on version 0.5.3.1 (latest as of posting date) but also on prior versions.

Reproducible: Always

Steps to Reproduce:
1. emerge ltrace
2.
3.

Actual Results:  
build complains about my_demangle missing while linking. 

Expected Results:  
clean build

Related warning during compilation of my_summary.c indicates the problem is that if USE_DEMANGLE is not set, the header files are not included, and the my_demangle call is never compiled. Cleanest solution is to ifdef/elseif around the call to my_demangle. 

But forwarded to author/package maintainer.
Comment 1 Otheus 2009-05-19 15:00:05 UTC
Created attachment 191785 [details, diff]
patch to resolve problem

This patch was tested against 0.5.3.1 of ltrace, which is normally MASKED. However, it should work the same or similarly to ltrace-0.4.
Comment 2 Dustin Polke 2009-05-19 15:06:41 UTC
It would be of much help if you could state which package you are talking about...
Comment 3 Otheus 2009-05-19 15:42:46 UTC
(In reply to comment #2)
> It would be of much help if you could state which package you are talking
> about...
> 

Surprisingly, there's no form field for that. I have now mentioned this in Summary.
Comment 4 Sebastian Luther (few) 2009-05-19 15:57:54 UTC
(In reply to comment #3)

> Surprisingly, there's no form field for that. I have now mentioned this in
> Summary.

That's where it belongs. And to make us more happy attach emerge --info and the complete build.log please.

Comment 5 Otheus 2009-05-19 15:59:55 UTC
> That's where it belongs. And to make us more happy attach emerge --info and the
> complete build.log please.

I would have, but after the patch worked, I couldn't figure out how to build a bad version.  

Comment 6 Mike Auty (RETIRED) gentoo-dev 2009-05-25 13:48:43 UTC
It would be very useful to us if you could recreate this problem and provide the build.log from the failed compilation attempt (providing the output from emerge --info should be the same whether you've applied the patch or not, so please post that even if you're having trouble recreating the problem).

Setting your system back to a state that isn't patched should be relatively easy (remove any ltrace ebuilds from your overlays, and any ltrace distfiles from /usr/portage/distfiles, then emerge --sync to ensure you have a clean copy of the ebuild and manifest and then rebuild ltrace).
Comment 7 Otheus 2009-05-25 14:35:15 UTC
"Setting your system back to a state that isn't patched should be relatively
easy"

Actually, it is quite difficult. Apparently, this bug happens when a particularly library (libiberty) is not installed, and since then, I've installed it and a bunch of things now require it. 

I've provided a patch... what more could you reasonably ask for?
Comment 8 Mike Auty (RETIRED) gentoo-dev 2009-05-25 14:49:56 UTC
Ideally we were hoping for a build.log or even just a copy of the compilation error you experienced, so that we could investigate the problem ourself.

We get a lot people submitting a lot of bugs and a lot of patches.  Sometimes the bugs only occur in certain circumstances and sometimes the patches are poor work-arounds for the actual problem.  By providing as much information about the problem as possible, it helps our maintainers figure out the best solutions for the problem.

I'll reassign this to the appropriate herd, but please be aware they may still require further information from you.
Comment 9 Otheus 2009-05-25 14:55:11 UTC
Right. Well, the actual bug is that someone inserted code to make ltrace not completely depend on this "demangle" feature, which requires a library, which may or may not be installed (the build for Gentoo may be the problem here). The patch simply checks for the "USE_DEMANGLE" configuration option (already set in the configure scripts); if not set, the demangle option is not checked and unconditionally, the name is printed without trying to demangle. 
Comment 10 Pacho Ramos gentoo-dev 2010-03-13 18:30:11 UTC
I cannot reproduce this with dev-util/ltrace-0.5.3.1
Comment 11 Pacho Ramos gentoo-dev 2012-10-22 17:57:11 UTC
(In reply to comment #10)
> I cannot reproduce this with dev-util/ltrace-0.5.3.1