Spec URL: http://roland.fedorapeople.org/cross-kernel-headers.spec I did not actually upload an srpm because it's large and almost entirely just the upstream kernel tarball, which everybody already has. I did upload a pkgs git repository at git://fedorapeople.org/~roland/cross-kernel-headers.git though. Description: This is an incarnation of the "kernel-headers" package for cross-compilation use with the cross-binutils and cross-gcc packages that already exist. For each binutils-TARGET this has a kernel-headers-TARGET that populates the toolchain sysroot with kernel header files. This is sufficient to cross-compile upstream glibc Fedora Account System Username: roland
With this and the cross-gcc, stock Fedora packages make it easy to build-test glibc for all architectures while doing development. I hope we can get this package or something like it in. It doesn't make sense to have a million individual packages of sys-root contents for Linux targets, since sysroots can be populated from real Fedora RPMs where they exist. But the cross-gcc and this cover many targets for which there are no Fedora builds. And the convenience of 'yum install gcc-* kernel-headers-*' being all you need to do cross-development for glibc is awesome for us. Also note this uses the upstream kernel verbatim, without even stable patches, let alone any of the patches in the Fedora kernel RPMs. For cross-development targetting the official kernel user ABIs this seems appropriate.
Koji scratch build for rawhide at https://koji.fedoraproject.org/koji/taskinfo?taskID=7106001
Sounds like a good idea. I don't think you can build glibc for all arches, but I guess you'd need this for uclibc or any other C library too.
Hmmm... I wonder if it would be worth building cross-gcc on top of this. This might let us build some of the missing libgcc's that require external headers.
I suspect that libgcc build need libc headers more than they need kernel headers. But that's neither here nor there as to getting this package review done and approved. Can we get it approved so I can add the package already?
RPMLINT: > $ rpmlint cross-kernel-headers.spec > cross-kernel-headers.spec:80: W: non-standard-group Development/System \ > cross-kernel-headers.spec:103: W: non-standard-group Development/System \ Using macros to generate headers. Should be OK IMO. > cross-kernel-headers.spec:169: W: macro-in-comment %{rpmprefix} Escape the %. > cross-kernel-headers.spec:216: W: mixed-use-of-spaces-and-tabs (spaces: line 216, tab: line 13) There's a stray space. > 0 packages and 1 specfiles checked; 0 errors, 4 warnings. VISUAL INSPECTION: %do_package mips-linux-gnu %{build_mips} mips64-linux-gnu ^^ Don't you mean %do_symlink?
pbrobinson's scratch build of linux-user-chroot?#b7afe5173cbd31b029b027b6f8a14baa5e6ce87a for epel7-archbootstrap and git://pkgs.fedoraproject.org/linux-user-chroot?#b7afe5173cbd31b029b027b6f8a14baa5e6ce87a failed http://koji.fedoraproject.org/koji/taskinfo?taskID=12089939
Close as the function is provided by kernel-cross-headers, a subpackage of kernel package. And any enhancement request can be posted against kernel package.