|
|
Re: Strategy for packaging an ARM Cortex-M toolchain |
On 05/25/2012 08:27 PM, Ralf Corsepius wrote:
Why have more than one gcc or binutils for arm-eabi at all? Just add multilibs for the extra variants of interest. You can even split the multilibs out into subpackages if it matters.This is simply not true. A gcc targeting glibc/linux is entirely different from a GCC targetting newlib and entirely different from a GCC targetting another OS.
Exactly. There only needs to be one for newlib arm-eabi- it doesn't need to be Cortex-M specific. There only needs to be one for arm-linux-gneabi. Having arm-gp2x-linux is more specific than necessary.
-- Brendan Conoboy / Red Hat, Inc. / blc@xxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
|
|