Joakim Tjernlund <[email protected]> wrote on 2013/05/02
22:27:04:
>
> I built a cross toolchain using crossdev, noting special I think. Then I
> created
> binary pkgs like so:
> CTARGET=powerpc-softfloat_4.5.3-linux-gnu
> export ROOT=/ PKGDIR=${PORTDIR}/pkgs/${CTARGET}/cross-tools
> quickpkg --include-config=y `qlist -IC cross-${CTARGET}`
>
> Installed these pkgs on another host using
> ACCEPT_KEYWORDS=~* emerge -aG \
> cross-powerpc-softfloat_4.5.3-linux-gnu/linux-headers \
> cross-powerpc-softfloat_4.5.3-linux-gnu/binutils \
> cross-powerpc-softfloat_4.5.3-linux-gnu/glibc \
> cross-powerpc-softfloat_4.5.3-linux-gnu/gcc \
> cross-powerpc-softfloat_4.5.3-linux-gnu/gdb
> Note the KEYWORDS, installing pkgs using crossdev directly doesn't care
> about KEYWORDS
> but installing the same as binary pkgs respects KEYWORDS, a bit
asymmetric
> but not a big deal
>
> However this is somewhat confusing, I had to run
> binutils-config powerpc-softfloat_4.5.3-linux-gnu-2.21.1
> manually after installing the binary pkgs, is that expected?
> I figured I should not have to do that.
> On a side note I can mention, installing a binary x86 binutils on a
amd64
> host requires CHOST:
> CHOST=i686-pc-linux-gnu binutils-config
> powerpc-softfloat_4.5.3-linux-gnu-2.21.1
>
> Finally, running gdb yields:
> # powerpc-softfloat_4.5.3-linux-gnu-gdb
> Python Exception <type 'exceptions.NameError'> name 'os' is not defined:
hmm, this appears to be a gdb issue, not crossdev. If I use gdb 7.5.1 it
works just fine.
> Oh, is there a difference using quickpkg vs. emerge --buildpkg ?
