Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 248719

Summary: app-dicts/qvortado: pre-stripped files found
Product: Gentoo Linux Reporter: Diego Elio Pettenò (RETIRED) <flameeyes>
Component: New packagesAssignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status: RESOLVED FIXED    
Severity: QA CC: chtof62
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 239866    

Description Diego Elio Pettenò (RETIRED) gentoo-dev 2008-11-25 02:09:01 UTC
Portage warns about pre-stripped files being installed into the image directory; this is a bad thing since it makes Portage's splitdebug feature useless, and it stops the users and the developers from looking into backtraces with full debug information available.

For the developers going to look into it, what you have to look out for, to
find what is stripping the files, is one of these conditions:

- explicit "strip" command run on the produced files;
- "install -s" command to install the binary files;
- "-Wl,-s" flag passed during linking

Remove the "strip" commands, remove the "-s" option at install, and remove
"-Wl,-s" and the problem should be gone.

Thanks,
Diego
Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-12-23 19:46:19 UTC
*** Bug 251855 has been marked as a duplicate of this bug. ***
Comment 2 Christophe LEFEBVRE 2010-03-10 22:14:55 UTC
app-dicts/qvortaro-0.3.1.ebuild has been replaced with app-dicts/qvortaro-0.4.1.ebuild in portage and there is no pre-stripped files in the version currently in portage.

This bug can be CLOSED.
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2010-07-09 13:35:18 UTC
(In reply to comment #2)
> app-dicts/qvortaro-0.3.1.ebuild has been replaced with
> app-dicts/qvortaro-0.4.1.ebuild in portage and there is no pre-stripped files
> in the version currently in portage.
> 
> This bug can be CLOSED.
> 

Yes, you are right. Fixed by 0.4.1.