| 1 |
El dom, 27-01-2013 a las 16:12 +0100, Michał Górny escribió: |
| 2 |
[...] |
| 3 |
> 5. Solutions to specific problems |
| 4 |
> --------------------------------- |
| 5 |
> |
| 6 |
> 1. x11-proto packages |
| 7 |
> |
| 8 |
> Those packages install headers to /usr/include and pkg-config files |
| 9 |
> to /usr/lib64. This supposedly means that the headers could be |
| 10 |
> ABI-specific; however, so far I haven't seen a single difference. |
| 11 |
> |
| 12 |
> Possible solutions: |
| 13 |
> |
| 14 |
> a) check the headers by hand, move pkg-config files to /usr/share, |
| 15 |
> |
| 16 |
> b) make the proto packages multilib. This will cause identical .pc |
| 17 |
> files to be installed to lib32 & lib64 but will also enable eclass |
| 18 |
> checks for header consistency. |
| 19 |
> |
| 20 |
|
| 21 |
Currently, emul packages can install /usr/lib32/pkgconfig files (when |
| 22 |
enabling "development" USE flag). This was added because, as emul sets |
| 23 |
tend to be obsolete in a few weeks, people compiling packages against |
| 24 |
its lib32 provided libs were getting build failures due "native" |
| 25 |
pkgconfig files (usually from newer libs) were being used. |
| 26 |
|
| 27 |
Regarding /usr/include, it looks harder to solve, current emul packages |
| 28 |
simply don't provide headers at all, but it caused issues like this in |
| 29 |
the past: |
| 30 |
https://bugs.gentoo.org/show_bug.cgi?id=299490 |
| 31 |
|
| 32 |
Maybe installing headers in other place would be interesting :/ |
Archives