diff options
| author |   Mike Frysinger <vapier@gentoo.org> | 2012-05-26 01:25:48 -0400 |
|---|---|---|
| committer | Mike Frysinger <vapier@gentoo.org> | 2012-05-31 01:43:38 -0400 |
| commit | 15ec45f4528a073d72039b66f239abebf6feb25a (patch) | |
| tree | d4d4bc52102879852f5f5038b61e3657845719b0 /TODO | |
| parent | crossdev: add an --env flag for common env settings (diff) | |
| download | crossdev-15ec45f4528a073d72039b66f239abebf6feb25a.tar.gz crossdev-15ec45f4528a073d72039b66f239abebf6feb25a.tar.bz2 crossdev-15ec45f4528a073d72039b66f239abebf6feb25a.zip | |
crossdev: split host and target ABIs
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>
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -1,11 +1,6 @@ - strip package.use.force (i.e. building x86_64 on x86_64 gets forced multilib) - filter /usr/CTARGET/ from revdep-rebuild #182601 -- HOST_ABI and TARGET_ABI selection; consider: - - build a 64bit (amd64) cross-compiler which targets 32bit (x86) - - build a 64bit (amd64) cross-compiler which targets x32 - - ABI variables atm do not differentiate between host - - package.use not getting setup correctly: # cat /etc/portage/package.use/cross-x86_64-cros-linux-gnu cross-x86_64-cros-linux-gnu/gdb sys-devel gdb |