I see with further experimentation that the ABINAME being 5 and
the patch-release that I want being 5 is probably just a coincidence.
I added 5 (literal) as an argument to patch_command and it seems to be
building without the extra patches. I haven't tried putting in
my change yet ... will report on whether that succeeds later.
bjb
On Sun, Nov 20, 2011 at 11:28:45AM -0500, Brenda J. Butler wrote:
Package: linux-source-2.6.32
Version: 2.6.32-38
Severity: normal
I'm running 2.6.32-5-xen-amd64 and I'd like to compile a new vmlinuz
with enhanced errno reporting (distinguish between ENOMEM returns
in fork.c). When I try to build 2.6.32-5, it applies all the patches
through 34squeeze1 (and actually fails to do that as one of the
later patches conflicts with my change).
What I did:
dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc
/usr/src/kernel-patches/all/2.6.32/apply/debian 5
cd linux-2.6-2.6.32
vi kernel/fork.c
fakeroot make -f debian/rules.gen binary-arch_amd64_xen
What happened:
(all the rest of the patches started to apply, and failed at version
14 where there was another edit to fork.c, so the build
failed)
What I expected:
A build without all the rest of the patches being applied.
Variant:
in What I did, I tried this also, and all the patches still got
applied:
dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc
/usr/src/kernel-patches/all/2.6.32/apply/debian 5
cd linux-2.6-2.6.32
vi kernel/fork.c
fakeroot make -f debian/rules.gen build_amd64_xen_amd64_real
I looked in the makefiles, and noted that in debian/rules.real, the
apply-patch command definition has no way to specify the patch-level:
define patch_cmd
cd '$(DIR)'; python '$(CURDIR)/debian/bin/patch.apply'
--overwrite-home='$(CURDIR)/debian/patches'
endef
Maybe the $(ABINAME) could be used to produce a patch-level for this
command?
I'm not all that familiar with building Debian kernels from source, I'd
be happy to learn the right way if I was doing it wrong. I was
following instructions from
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
and supplemented it by reading the makefiles.
bjb
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-source-2.6.32 depends on:
ii binutils 2.20.1-16 The GNU assembler, linker and
bina
ii bzip2 1.0.5-6high-quality block-sorting file
co
Versions of packages linux-source-2.6.32 recommends:
ii gcc 4:4.4.5-1 The GNU C compiler
ii libc6-dev [libc-dev] 2.11.2-10 Embedded GNU C Library:
Developmen
ii make 3.81-8 An utility for Directing
compilati
Versions of packages linux-source-2.6.32 suggests:
ii kernel-package12.036+nmu1A utility for building Linux
kerne
ii libncurses5-dev [ncurses- 5.7+20100313-5 developer's libraries and docs
for
pn libqt3-mt-dev none (no description available)
-- no debconf information
---end quoted text---
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
