First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 144700
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Toolchain Maintainers <toolchain@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: SpanKY <vapier@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 144700 depends on: Show dependency tree
Show dependency graph
Bug 144700 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-08-21 16:34 0000
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 From SpanKY 2006-08-21 16:40:37 0000 -------
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 From SpanKY 2006-08-27 02:16:48 0000 -------
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 From SpanKY 2006-08-27 10:53:13 0000 -------
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 ...

First Last Prev Next    No search results available      Search page      Enter new bug