https://bugzilla.redhat.com/show_bug.cgi?id=766166 --- Comment #17 from David Howells <dhowells@xxxxxxxxxx> --- (In reply to comment #13) > So my question is: what would it take or is it even feasable to provide a > cross-libgcc along with the cross-gcc and cross-binutils packages? This > would make the existing cross packages a lot more useful for embedded > hardware bringup development. The problem is that adding userspace is massively multiplicative, especially for some arches. Some libgccs won't build without bits of kernel headers or C library headers - and there are multiple C libraries that would have to be included in the SRPM as not all arches are supported by all C libraries. At least I'd probably have to include glibc and uClibc. And then, which libgccs do we build? MIPS, for example, has half a dozen, I think, and FRV has three or four. It may be possible to cheat and only include a few headers and not build shared-library libgccs. It may even be worth considering build userspace packages for certain useful combinations if we can keep the list small. However, my primary objective is to build as many compilers as I can for the purpose of building the Linux kernel - even if I can't *link* the kernel due to the lack of a libgcc. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review