Agustin Henze <tin@debian.org> writes: > Yes, I agree it's better separate the libc in another package. I'll take a look > to pdclib, I've always used newlib and I never tried another. I'm not sure I can really recommend pdclib; it was easy for me to build and is sufficient for what I'm building, but it's far from a 'great' libc. And, upstream seems to have abandoned it. > Great! :). I can do this, gcc has integration with newlib and it isn't too > hard, I did it other times and with a little patience it works. I'm using > gcc+newlib for a while (with a cortex-M3) and it works very well. I'll try > newlib-nano too, seems pretty good idea. I don't think I want to use the gcc newlib integration though; I'd rather have libc packaged separately and not linked to gcc at all. However, I do think any newlib packaging should respect the multi-lib stuff in the gcc build so that -lc would 'just work' with the appropriate compiler flags. > It's great, I want to see a good toolchain for bare metal in debian :) and I > can help with this. Are you using collab-maint? If not, could you > upload it there? I've git it on alioth; could easily move to collab maint. -- keith.packard@intel.com
Attachment:
pgpf6SPOiZqO8.pgp
Description: PGP signature