| 1 |
On Wed, 3 May 2017 12:05:48 +0200 |
| 2 |
"Paweł Hajdan, Jr." <phajdan.jr@g.o> wrote: |
| 3 |
|
| 4 |
> I encountered <https://bugs.gentoo.org/show_bug.cgi?id=617276> while |
| 5 |
> working on some cross-compiling project. |
| 6 |
> |
| 7 |
> Admittedly, it may not be that easy to handle host package |
| 8 |
> dependencies fully automatically. |
| 9 |
> |
| 10 |
> I'm wondering - is it documented what portage guarantees, and what I'm |
| 11 |
> expected to just manually handle to provide host build dependencies? |
| 12 |
> |
| 13 |
> Any other advice about properly using crossdev would also be |
| 14 |
> appreciated. I'd be happy to test and help improve things. |
| 15 |
|
| 16 |
|
| 17 |
From man emerge: |
| 18 |
|
| 19 |
|
| 20 |
--root-deps[=rdeps] |
| 21 |
If no argument is given then build-time dependencies of |
| 22 |
packages for ROOT are installed to ROOT instead of /. If the |
| 23 |
rdeps argument is given then discard all build-time dependencies |
| 24 |
of packages for ROOT. This option is only meaningful when used |
| 25 |
together with ROOT and it should not be enabled under normal |
| 26 |
circumstances! |
| 27 |
|
| 28 |
Does not affect EAPIs that support HDEPEND. Experimental |
| 29 |
EAPI 5-hdepend provides HDEPEND as a new means to adjust |
| 30 |
installation into "/" and ROOT. If ebuilds using EAPIs |
| 31 |
which do not support HDEPEND are built in the same |
| 32 |
emerge run as those using EAPIs which do support HDEPEND, |
| 33 |
this option affects only the former. |
| 34 |
|
| 35 |
|
| 36 |
crossdev wrappers set --root-deps=rdeps (read cross-emerge, this can be |
| 37 |
overriden), but be careful: If you only care about getting all the deps |
| 38 |
and maybe more then removing --root-deps might help you. However, when |
| 39 |
cross compiling you will likely run into broken deps since / and ROOT |
| 40 |
will not use the same keyword visibility. |
Archives