All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin-Éric Racine" <martin-eric.racine@iki.fi>
To: linux-kbuild@vger.kernel.org
Cc: debian-kernel@lists.debian.org
Subject: 'make deb-pkg' generates a linux-headers-(version) that skips some files
Date: Wed, 11 Jul 2012 16:14:08 +0300	[thread overview]
Message-ID: <CAPZXPQfE7M0Jzsns4zKrKu0x55_AWEUpzydm1dUOshhZo_ki=A@mail.gmail.com> (raw)

Greetings,

As a part of the debugging process for (
http://bugs.debian.org/677533/ ), I was asked to build myself a kernel
from HEAD, followed by standalone modules from an external tree,
following this procedure:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git fetch origin
git reset --hard origin/master
cp /boot/config-$(uname -r) .config
scripts/config --disable DEBUG_INFO
make localmodconfig
make deb-pkg
sudo dpkg -i ../linux-image-3.5.0*.deb ../linux-headers-3.5.0*.deb
cd ..
wget http://moinejf.free.fr/gspca-2.15.18.tar.gz
tar -zxf gspca-2.15.18.tar.gz
cd gspca-2.15.18
make
sudo make install

Compilation of the standalone modules failed, because the
linux-headers package produced by 'make deb-pkg' failed to include
(arch/x86/Makefile_32.cpu), which had to be copied by hand to complete
the build.

I'm not sure whether this is due to an oversight or whether this is a
regression, much even less whether this is an upstream LKML issue or a
Debian issue, so I'm CC'ing both lists.

Hopefully, someone can figure out what went wrong and fix it.

Cheers!
Martin-Éric

             reply	other threads:[~2012-07-11 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:14 Martin-Éric Racine [this message]
2012-07-11 13:46 ` 'make deb-pkg' generates a linux-headers-(version) that skips some files maximilian attems
2012-07-11 14:00   ` Martin-Éric Racine

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='CAPZXPQfE7M0Jzsns4zKrKu0x55_AWEUpzydm1dUOshhZo_ki=A@mail.gmail.com' \
    --to=martin-eric.racine@iki.fi \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@vger.kernel.org \
    /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.