| 1 |
On 18-07-2014 14:46:46 +0200, Anders Bo Rasmussen wrote: |
| 2 |
[snip searchpath: prefix followed by host] |
| 3 |
> That worries me some as it means that when we compile our software it |
| 4 |
> might mean that something is comming from outside of the Gentoo Prefix |
| 5 |
> installation as it contains paths such as /usr/include and /lib64 |
| 6 |
> which is outside Gentoo Prefix. |
| 7 |
> |
| 8 |
> Is there a good way to avoid this? |
| 9 |
|
| 10 |
You will need the host paths for many things, unless you're on RAP, I |
| 11 |
guess. Best example is the system headers and libc, of which you showed |
| 12 |
examples below. |
| 13 |
|
| 14 |
We try to avoid having links against the host-provided components, but |
| 15 |
we cannot enforce this, currently. |
| 16 |
|
| 17 |
Fabian |
| 18 |
|
| 19 |
|
| 20 |
> I've checked on gvim how much comes from outside in my installation of |
| 21 |
> Gentoo Prefix: |
| 22 |
> |
| 23 |
> $ldd /usr/local/nangate/tools/gentoo-prefix-test/usr/bin/gvim | wc -l |
| 24 |
> 53 |
| 25 |
> $ldd /usr/local/nangate/tools/gentoo-prefix-test/usr/bin/gvim | grep |
| 26 |
> -v gentoo-prefix-test |
| 27 |
> linux-vdso.so.1 => (0x00007fffda1fd000) |
| 28 |
> libm.so.6 => /lib64/libm.so.6 (0x0000003c6b600000) |
| 29 |
> libdl.so.2 => /lib64/libdl.so.2 (0x0000003c6be00000) |
| 30 |
> libc.so.6 => /lib64/libc.so.6 (0x0000003c6b200000) |
| 31 |
> librt.so.1 => /lib64/librt.so.1 (0x0000003c6c600000) |
| 32 |
> libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003c6c200000) |
| 33 |
> /lib64/ld-linux-x86-64.so.2 (0x0000003c6ae00000) |
| 34 |
> libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003c73800000) |
| 35 |
> libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003c7d800000) |
| 36 |
> libutil.so.1 => /lib64/libutil.so.1 (0x0000003c79400000) |
| 37 |
> libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003c75800000) |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Fabian Groffen |
| 42 |
Gentoo on a different level |
Archives