public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: Michal Marek <mmarek@suse.cz>
Cc: 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,
	"Ben Hutchings" <ben@decadent.org.uk>
Subject: Re: [PATCH] kbuild: create linux-headers package in deb-pkg
Date: Thu, 13 Jan 2011 14:38:41 +0000	[thread overview]
Message-ID: <20110113143840.GN20262@vostochny.stro.at> (raw)
In-Reply-To: <4D2F044E.7060607@suse.cz>

On Thu, Jan 13, 2011 at 02:55:26PM +0100, Michal Marek wrote:
> On 10.1.2011 18:46, maximilian attems wrote:
> >>> +find . -name Makefile -o -name Kconfig\* -o -name \*.pl > /tmp/files$$
> >>> +find arch/x86/include include scripts -type f >> /tmp/files$$
> >> x86 centric?
> > 
> > this will break on any non x86 arch, what is the correct variable
> > for $ARCH?
> 
> This should be changed to arch/$SRCARCH/include.

thanks for the pointer, sent patch, that was the easy part.
 
 
> >>> +tar -c -f - -T /tmp/files$$ | (cd $destdir; tar -xf -)
> >>> +(cd $objtree; tar -c -f - -T /tmp/objfiles$$) | (cd $destdir; tar -xf -)
> >>> +rm -f /tmp/files$$ /tmp/objfiles$$
> >>> +arch=$(dpkg --print-architecture)
> >>> +
> >>> +cat <<EOF >> debian/control
> >>> +
> >>> +Package: $hdrpackagename
> >>> +Provides: linux-headers, linux-headers-2.6
> >>> +Architecture: $arch
> >> not sure if that will interfere with the new crosscompile feature
> >> of deb-pkg in linux-next.
> > 
> > aboves arch call seems redundant with what we already have.
> 
> Yes, please remove it. 

will look at it again in a calmer moment.

> 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.

-- 
maks

  reply	other threads:[~2011-01-13 14:38 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 [this message]
2011-01-18 19:52         ` Ben Hutchings

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=20110113143840.GN20262@vostochny.stro.at \
    --to=max@stro.at \
    --cc=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox