All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: maximilian attems <max@stro.at>
Cc: "Michal Marek" <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	linux-kernel@vger.kernel.org,
	"Ralf Rösch" <ralf.roesch@rw-gmbh.de>,
	debian-kernel@lists.debian.org
Subject: Re: [PATCH] kbuild: create linux-headers package in deb-pkg
Date: Tue, 18 Jan 2011 19:52:58 +0000	[thread overview]
Message-ID: <20110118195258.GA21934@decadent.org.uk> (raw)
In-Reply-To: <20110113143840.GN20262@vostochny.stro.at>

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

      reply	other threads:[~2011-01-18 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 14:42 [PATCH] kbuild: create linux-headers package in deb-pkg Theodore Ts'o
2010-12-25 11:20 ` maximilian attems
2010-12-29 13:07   ` Michal Marek
2011-01-10 17:46   ` maximilian attems
2011-01-13 13:55     ` Michal Marek
2011-01-13 14:38       ` maximilian attems
2011-01-18 19:52         ` Ben Hutchings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110118195258.GA21934@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --cc=mmarek@suse.cz \
    --cc=ralf.roesch@rw-gmbh.de \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.