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:
warning:
Could not load the Python gdb module from `/usr/share/gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.
GNU gdb (Gentoo 7.6 p1) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <
http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu
--target=powerpc-softfloat_4.5.3-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>.
(gdb)
This one I haven't figured out yet, what is up with the python connection
here?
Oh, is there a difference using quickpkg vs. emerge --buildpkg ?
Jocke
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:
warning:
Could not load the Python gdb module from `/usr/share/gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.
GNU gdb (Gentoo 7.6 p1) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <
http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu
--target=powerpc-softfloat_4.5.3-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>.
(gdb)
This one I haven't figured out yet, what is up with the python connection
here?
Oh, is there a difference using quickpkg vs. emerge --buildpkg ?
Jocke