Summary: | Cross compiling: attempting to cross compile will result in installing onto host system | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dave Bender <codehero> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dave Bender
2008-04-28 20:18:16 UTC
Probably same as http://forums.gentoo.org/viewtopic-p-3872156.html#3872156 -> INVALID (keeping this open in case I'm wrong). (In reply to comment #1) > Probably same as http://forums.gentoo.org/viewtopic-p-3872156.html#3872156 -> > INVALID (keeping this open in case I'm wrong). > Marius, While I believe that this discussion is relevant to this bug, hagra's solution to the problem was highly dependent on the circumstances. This is does not resolve the question as to why portage installs baselayout (or any other dependencies) into the host system. Look at it this way: the build host should NOT have to have baselayout2 in order to install it onto a target. While I understand that there are some dependencies that should be in the host system (basic cross compiling tools, perl, etc) those dependencies are distinct from packages that need to be installed in the target system. Is there any way to distinguish dependencies like this in portage? Dave *** This bug has been marked as a duplicate of bug 174552 *** |