| Summary: | sys-apps/paludis: fails to find boost without (deprecated) eselect-boost | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
| Component: | Current packages | Assignee: | Robert Piasek (RETIRED) <dagger> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | A simple work-around for the build system | ||
Created attachment 326928 [details, diff] A simple work-around for the build system Nowadays eselect-boost symlinks are deprecated and packages are supposed to be able to find out the newest boost themselves (like boost.m4 does). For those unable of achieving that themselves or requiring older boost version (than the newest one), there's boost-utils.eclass. Sadly, paludis does use really poor custom code which neither is capable of finding boost nor accepting an include path and library suffix from user. Thus, it all falls back to pushing compatibility -I & -L flags. I'm attaching a simple patch which does exactly that. The proper fix would be probably to use the macros from sys-devel/boost-m4 which are able to correctly both detect the newest boost and accept an older version (through BOOST_ROOT).