| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
URL: http://bugs.gentoo.org/420089
Reported-by: Maciej Szmigiero <mhej@o2.pl>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
|
| |
We've handle forced USE flags for a while, and we've add the cross
paths to the revdep-rebuild filters, so these TODO entries are done!
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
If the xVER variable isn't set, we only add 4 args to the array, and
the subsequent shift of 5 would fail. So we'd end up treating the
previous args as USE flags and add them to package.use. Make this
work as intended by quoting the VER variable.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current ABI env var system does not differentiate between the ABI
of the CHOST (where things run) and the ABI of the target (what we're
generating code for). This makes it difficult to build a toolchain
that runs on ABI=amd64 but targets ABI=x32.
Introduce a TARGET_ABI set of variables that the tools that run on the
CHOST can use to figure out what ABIs it needs to build for the CTARGET.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
| |
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|