Cross-Compiling RPi Ports From amd64 Using Native Toolchain

[Jeremy Brown]

One additional thing: I checked my toolchain and did see that some of my
programs (ar, as, cc, gcc, ld, ranlib) are statically linked, whereas the
rest are dynamically linked, including cpp and nm which also gave me the
ELF interpreter error. So I'll change my question somewhat - if I use the
command given on the qemu page (env -u TARGET -u TARGET_ARCH make -j 4
toolchain) instead of the one provided by crochet (make XDEV=${XDEV}
XDEV_ARCH=${XDEV_ARCH} WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 WITHOUT_CLANG=1
WITHOUT_CLANG_BOOTSTRAP=1 WITHOUT_CLANG_IS_CC=1 WITHOUT_TESTS=1 xdev),
would I be more likely to succeed in cross-compiling my ports and will I be
able to use this toolchain to build the kernel and world with crochet?

-Jeremy

On Fri, Jan 2, 2015 at 6:06 PM, Jeremy Brown <mischif at mischivous.com> wrote:

> I followed the steps crochet made me do, so my setup is a bit different than what is shown on that page - I used make xdev instead of make toolchain assuming the commands were equivalent, but if not please let me know.
>
> I was left with tools in two places - /usr/armv6-freebsd and /usr/obj/armv6-freebsd. It seems most of the important elements such as the compilation tools are in the former location, with only sourcefiles in the latter.
>
> I have to copy the tools over into /usr/armv6-freebsd in the chroot and not /usr/obj because my version of gcc doesn't pick up on other directories to search, should I just copy /usr/obj/armv6-freebsd/usr/src/tmp to /usr/armv6-freebsd in the chroot?
>
> When I would try to set the environment variables make would never pick them up - I would try either modifying /root/.profile and use sh as my shell or modifying /root/.cshrc and using csh as my shell. Thankfully, the host's PATH would overwrite the PATH in the chroot, so I could add /usr/armv6-freebsd to my path and make would pick up the new tools.
>
> Also, since building the ports is to be scripted, I'm using make from the host using DESTDIR to set up a chroot, is there some superior way to do this?
>
> -Jeremy
>
> >* I managed to use crochet and the QemuUserModeHowTo to build some
> *>* ports for the RPi.  What bit me in the process was that the "Cross
> *>* Building Using The Host Cross Compiler" section had to be followed
> *>* to a T - in particular, the built cross toolchain in
> *>* /usr/obj/usr/src/tmp must be moved to <chroot_root>/usr/obj
> *>* wholesale, the local headers symlink made, and the cross-CC
> *>* environment variables set up.  The error in #2 above seems to
> *>* indicate that the cross tool is not statically linked, so maybe the
> *>
> * wrong toolchain is in use.*
>
>