[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bug with kernel compilation

>>"Nick" == Nick Phillips <nwp@lemon-computing.com> writes:

 Nick> It appears that when I previously posted
 Nick> (http://lists.debian.org/debian-devel/2001/debian-devel-200112/msg00703.html),
 Nick> I may have been less delusional than it first appeared; I've just had
 Nick> someone else asking whether I know of a workaround, as they're having
 Nick> the same problem.

	So I went back and looked at your original message.

 Nick>  It appears that the debian/rules in kernel-source-2.2.19 calls dpkg as
 Nick>  follows:
 Nick>  CC= dpkg --print-architecture

__> egrep CC= /usr/share/kernel-package/rules 
  #architecture:=$(shell CC=$(HOSTCC) dpkg --print-gnu-build-architecture)

	Hmm. This is a commented out line.

__> egrep 'dpkg ' /usr/share/kernel-package/rules 
  #architecture:=$(shell CC=$(HOSTCC) dpkg --print-gnu-build-architecture)
NEED_BIN86 := $(shell if dpkg --compare-versions \
        dpkg --build $(SOURCE_TOP) $(DEB_DEST)
        dpkg --build $(HEADER_TOP) $(DEB_DEST)
        dpkg --build $(DOC_TOP) $(DEB_DEST)
        dpkg --build $(IMAGE_TOP) $(DEB_DEST)

	Again, no hits. So, the solution: upgrade to a more recent
 kernel-package, run make-kpkg clean, and try again.

 Nick> I was using --flavour at the time. I'm not yet sure whether they are.

 Nick> I'm not entirely sure how the kernel-package stuff is supposed
 Nick> to work, but my *guess* is that the debian/rules in the kernel
 Nick> source directory is not getting updated from one provided by
 Nick> the kernel-package package.

	If a ./debian dir is present, you are describing the designed
 behaviour. Running make-kpkg clean (like the make-kpkg docs tell one
 to do repeatedly) would solve the problem.

 Nick> Anyway, it appears that this is a real (as opposed to
 Nick> imaginary) problem; I just don't know whether it's dpkg,
 Nick> kernel-package, kernel-source-*, or "something else" that
 Nick> causes it.

	Pilot error? (not running make-kpkg clean)

 Nick> Clues? Suggested actions (e.g. bug-filing, but against what? /
 Nick> suggest that the guy who contacted me contacts Manoj? /
 Nick> whatever?), if any?

	Well, sure, he can contact me, but see if running make-kpkg clean 
 resolves it first.

 Gordon's first law: If a research project is not worth doing, it is
 not worth doing well.
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: