Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 144700 - cross-compilers should install into /usr/CHOST/CTARGET/*bin/ rather than /usr/CTARGET/*bin
Summary: cross-compilers should install into /usr/CHOST/CTARGET/*bin/ rather than /usr...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-21 16:34 UTC by SpanKY
Modified: 2006-08-27 10:53 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SpanKY gentoo-dev 2006-08-21 16:34:14 UTC 
currently our binutils/gcc cross-compilers install their binaries into /usr/CTARGET/binutils-bin and /usr/CTARGET/gcc-bin ... this is a bit confusing now that we have switched fully to a sysroot system where /usr/CTARGET is our sysroot

the more standard method would be to install into /usr/CHOST/CTARGET/binutils-bin and /usr/CHOST/CTARGET/gcc-bin ... this would also keep /usr/CTARGET completely clean of any CHOST files
Comment 1 SpanKY gentoo-dev 2006-08-21 16:40:37 UTC 
Jocke pointed out:
packages install into /usr/CTARGET/{gcc,binutils}-bin and then the binutils-config script sets up /usr/CTARGET/bin ... all need to move
Comment 2 SpanKY gentoo-dev 2006-08-27 02:16:48 UTC 
ok ive updated toolchain-binutils.eclass and released binutils-config-1.9

cross-compiler binutils will no longer touch /usr/CTARGET (and in fact, after reviewing all of this, it was wrong for me to have the stuff install into /usr/CTARGET as the libs from binutils are in *CHOST* format, not *CTARGET*)

i'll see about gcc later today
Comment 3 SpanKY gentoo-dev 2006-08-27 10:53:13 UTC 
ok gcc was painless because it all filters down :)

i'll be releasing binutils-config-1.9-r1 to correct a PATH issue, but otherwise that should be it hopefully ...