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.

> > The only reason gcc/cpp are required are to strip the embedded Ruby code out
> > before handing to the assembler, we can achieve the same by opening a 
> > multiline
> > comment around the ruby instead. Care needs to be taken not to close the
> > comment prematurely hence "*/" is written in the one place it is used as
> > "\x2a/" (i.e. encoding the * in hex). Having done this we can pass the .S 
> > file
> 
> We could probably do this even without relying on magic ASCII numbers.
> Using something like printf("%s%s", "*", "/"). But since I'm not aware
> of any relevant non-ASCII compatible system, either way is fine.

Right, I also considered a function comment(fmt, ...) which wrapped wha
t it was given in the /* */ in some opaque way but for the one instance
in this code I thought it wasn't worth it.

> 
> Acked-by: Siarhei Siamashka <[email protected]>

Thanks.

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.

Reply via email to