[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#561046: ITP: gcc-arm -- The GNU C Compiler (cross-compiler for ARM targets)


2009/12/14 Bill Gatliff <bgat@billgatliff.com>:
>> How 'arm-none-eabi' differ from 'arm-linux-gnueabi' besides C library?
>> Can 'arm-linux-gnueabi' be used in most 'arm-none-eabi' use cases?
> It is technically possible to use an arm-linux toolchain where one would
> normally use an arm-none toolchain.  But there are subtle differences
> between the two at the library interface level, I have found that the
> *-linux toolchain tends to depend on library functions that bare-metal
> systems often don't have.
> It's also a matter of clarity for developers.  "Why would I want a
> *-linux toolchain, I'm not building for a Linux target".

But if technically speaking, they both offer same resources for
developers, it does not make me any sense to duplicate the archive.

>> Emdebian is a group of people. This group tries to dignify Debian to
>> be used for embedded targets (not fork, nor port). There are many
>> tools (scratchbox, qemu, cross toolchains, apt-cross, dpkg-cross,
>> emdebian-{tools, rootfs, grip, *}) emdebian people is working on.
> Yes, and they are all fabulous.  Particularly if you are trying to
> manage Debian in cross-platform environments.  But they aren't
> particularly optimal for what the OP is trying to accomplish, which is
> to produce a toolchain that can be used as a starting point for a
> bare-metal application.

This is like a first stage toolchain, which it is in the toolchain
roadmap (as bootstrapping toolchain). Then we can have eglibc, uclibc
or other C libraries based toolchains.

> I like the idea of having cross toolchain packages that are "sociable"
> with the Debian system.  However, that really isn't a consideration for
> a binutils-arm-none toolchain: its work products are by definition not
> compatible with Debian--- or even Linux.  So the concerns for this
> situation come down to making sure that his packaging approach is
> consistent with other Debian packages for non-Debian toolchains, AFAICT.

I think I missed this point on binutils-arm-none. But binutils does
not depend on linux nor C library. binutils-armel can be shared among
(eglibc,uclibc,newlib,...) toolchains.

 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

Reply to: