Bug 1116177
Summary: | Review Request: cross-kernel-headers - Header files for the Linux kernel for use by glibc | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roland McGrath <roland> |
Component: | Package Review | Assignee: | Siddhesh Poyarekar <siddhesh> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | codonell, dhowells, i, mnewsome, package-review, robinlee.sysu |
Target Milestone: | --- | Flags: | spoyarek:
fedora-review?
|
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 07:24:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roland McGrath
2014-07-04 01:23:36 UTC
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. |