On Thu, 2015-08-13 at 10:21 +0200, Olliver Schinagl wrote: > Hey, > > On 13-08-15 09:55, Ian Campbell wrote: > > On Thu, 2015-08-13 at 10:24 +0300, Siarhei Siamashka wrote: > > > On Tue, 4 Aug 2015 20:01:39 +0100 > > > Ian Campbell <[email protected]> wrote: > > > > > > > A cross-binutils is generally a bit easier to get hold of, and in > > > particular > > > > binutils-none-eabi (and binutils-arm-linux-gnueabi{,hf}) are > > > available in > > > > Debian Jessie while the equivalent cross gcc is not. > > > Just curious. How does one normally build U-Boot or kernel for ARM > > > devices in Debian Jessie? > > The official .deb packages are built natively in Debian, not cross > > compiled. > > > > For user's local cross builds there is work on going to provide > > official packaged cross compilers but those are not widely available > > enough (and somewhat in flux, and not in a stable release yet) to rely > > on for the sunxi-tools package builds. > > > > For non-packaging work I personally tend to use the Linaro compilers > > and will switch to the officially package cross-compilers once they are > > more reliably available. > I think i'm using the embdebian cross toolchain (unless it has been > added to jessie) and I'm not unhappy with it so far. Though I do only > crossbuild the kernel and u-boot and my own little userspace app.
Yes, I think the embdebian stuff was a bit moribund when I happened to be looking (several years ago now). These days I think the same people are mostly looking at getting something into Debian proper, that's described at https://wiki.debian.org/CrossToolchains Ah, and that points to embdebian for Jessie, which explains why that is no longer stale and you are using it ;-) I should probably switch, since a packaged compiler would be nicer, but I still wouldn't be able to use it for the official package builds. Ian. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
