linux-kernel - Re: [PATCH] kbuild: create linux-headers package in deb-pkg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 18 Jan 2011 19:52:58 +0000
From:	Ben Hutchings <ben@...adent.org.uk>
To:	maximilian attems <max@...o.at>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kbuild@...r.kernel.org,
	Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org,
	Ralf Rösch <ralf.roesch@...gmbh.de>,
	debian-kernel@...ts.debian.org
Subject: Re: [PATCH] kbuild: create linux-headers package in deb-pkg

On Thu, Jan 13, 2011 at 02:38:41PM +0000, maximilian attems wrote:
> On Thu, Jan 13, 2011 at 02:55:26PM +0100, Michal Marek wrote:
[...]
> > BTW, here is a bugreport I got privately about
> > the very same issue:
> > On 12.1.2011 10:02, Ralf Rösch wrote:
> > | [...]
> > | Attached you will find a patch to complete the build successfully for my
> > | mipsel target.
> > | The dpkg --print-architecture shows i386 which results in error:
> > | dpkg-gencontrol: Fehler: aktuelle Host-Architektur »mipsel« erscheint
> > | nicht in der Architekturliste (i386) des Pakets
> > | (current host architecture 'mipsel' does not appear in package's list
> > i386)
> > | so I changed "arch" temporary to "any".
> > |
> > | It would be nice if it would be possible to make the kernel-headers
> > | installable on any host.
> > | They are needed very frequently for cross-compiling. (I already possible
> > | with dpkg force).
> 
> Added Ben Hutchings and d-kernel on Cc. I do not use OOT modules, so
> I don't have a strong word on that, but from what I see in Debian
> they are arch specific.

Kernel header packages should be labelled with the target architecture.
This is because the headers include some generated files that are both
architecture- and configuration-specific.

Any package of libraries or headers for some architecture is in theory
useful for cross-development on any other architecture, yet we do not
label them as architecture: all.  If we did that, we would then have to
use a different name and installation path for each target so that they
are co-installable; this would also bloat the package list files.  You
should normally be able to convert a package for use in cross-
development using dpkg-cross, which changes its name and paths
accordingly.  However I don't know how well this will work for kernel
headers.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/