| Summary: | libiconv external recipe has RPATH QA issue | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> | ||||||
| Component: | devtools / tool chain | Assignee: | Bogdan Marinescu <bogdan.a.marinescu> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Low | CC: | bluelightning, john.toomey, meta.mr.watcher, meta.watcher, richard.purdie | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 1.4 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | --- | |||||||
| Attachments: |
|
||||||||
|
Description
Paul Eggleton
2012-06-27 15:46:16 UTC
This recipe is only used in uclibc configuration which is why this is only seen in certain cases. Interesting - FWIW, the report was from a user building a custom recipe for "dcmtk" that apparently was not working in conjunction with the libiconv built into eglibc. I did not dig further but I don't think they were using uclibc at all. OK, ignore my previous comment. Would it make sense to skip this recipe unless uclibc is being used? A fix was merged to disable the libiconv recipe when using eglibc: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8a2664b1c2f7ad6d34714d87ff78c02b4af99562 However for uclibc users we still need to fix the QA issue. Created attachment 1066 [details]
Patch to remove RPATH from libiconv.
Here's a quick and dirty patch to get past this on uclibc.
Created attachment 1067 [details]
Corrected uclibc patch
Previous patch had a line cut short.
Björn's patch has now been merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=00a2411470b989ca80bc2a6de08d105bc400dae5 |