1 |
Joakim Tjernlund <joakim.tjernlund@×××××××××.se> wrote on 2013/05/02 |
2 |
22:27:04: |
3 |
> |
4 |
> I built a cross toolchain using crossdev, noting special I think. Then I |
5 |
|
6 |
> created |
7 |
> binary pkgs like so: |
8 |
> CTARGET=powerpc-softfloat_4.5.3-linux-gnu |
9 |
> export ROOT=/ PKGDIR=${PORTDIR}/pkgs/${CTARGET}/cross-tools |
10 |
> quickpkg --include-config=y `qlist -IC cross-${CTARGET}` |
11 |
> |
12 |
> Installed these pkgs on another host using |
13 |
> ACCEPT_KEYWORDS=~* emerge -aG \ |
14 |
> cross-powerpc-softfloat_4.5.3-linux-gnu/linux-headers \ |
15 |
> cross-powerpc-softfloat_4.5.3-linux-gnu/binutils \ |
16 |
> cross-powerpc-softfloat_4.5.3-linux-gnu/glibc \ |
17 |
> cross-powerpc-softfloat_4.5.3-linux-gnu/gcc \ |
18 |
> cross-powerpc-softfloat_4.5.3-linux-gnu/gdb |
19 |
> Note the KEYWORDS, installing pkgs using crossdev directly doesn't care |
20 |
> about KEYWORDS |
21 |
> but installing the same as binary pkgs respects KEYWORDS, a bit |
22 |
asymmetric |
23 |
> but not a big deal |
24 |
> |
25 |
> However this is somewhat confusing, I had to run |
26 |
> binutils-config powerpc-softfloat_4.5.3-linux-gnu-2.21.1 |
27 |
> manually after installing the binary pkgs, is that expected? |
28 |
> I figured I should not have to do that. |
29 |
> On a side note I can mention, installing a binary x86 binutils on a |
30 |
amd64 |
31 |
> host requires CHOST: |
32 |
> CHOST=i686-pc-linux-gnu binutils-config |
33 |
> powerpc-softfloat_4.5.3-linux-gnu-2.21.1 |
34 |
> |
35 |
> Finally, running gdb yields: |
36 |
> # powerpc-softfloat_4.5.3-linux-gnu-gdb |
37 |
> Python Exception <type 'exceptions.NameError'> name 'os' is not defined: |
38 |
|
39 |
|
40 |
hmm, this appears to be a gdb issue, not crossdev. If I use gdb 7.5.1 it |
41 |
works just fine. |
42 |
|
43 |
> Oh, is there a difference using quickpkg vs. emerge --buildpkg ? |