Your message dated Fri, 05 Oct 2007 23:13:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Dependencies in packages built by kernel-package
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kernel-package
Version: 10.067
I needed to manually install the libc6-dev package to be able to use the
command: `make-kpkg binary-arch`
Otherwise, I get these kinds of errors:
scripts/basic/fixdep.c:107:23: error: sys/types.h: No such file or directory
scripts/basic/fixdep.c:108:22: error: sys/stat.h: No such file or directory
scripts/basic/fixdep.c:109:22: error: sys/mman.h: No such file or directory
scripts/basic/fixdep.c:110:20: error: unistd.h: No such file or directory
scripts/basic/fixdep.c:111:19: error: fcntl.h: No such file or directory
This is in sarge.
Thanks,
Charles
--- End Message ---
--- Begin Message ---
Hi,
Thanks for your report.
kernel-package has always been version agnostic, and does not
ever pretend to contain all dependencies that are required to build
kernels. The documentation building requirements are fairly large,
and only relevant for recent kernels.
Every linux kernel has minimum requirements, as stated in the
Documentation/Changes file. These requirements, for gcc, make,
binutils, modutils, e2fsporogs, util-linux, etc, with minimum version
numbers that change from version to version (so reading can't be
avoided while building a kernel). It is not practical for
kernel-package to track all the requirements, and to change as the
requirements change. Compiling kernels still remains an activity
that requires care, and one still needs to read through documentation
of the kernel and modules in order to ensure that one gets a working
kernel. I strongly recommend that people compiling kernels should
read these docs ;-) Not having module-init-tools is only the smallest
of gotchas in a kernel compile.
This is not an omission, this has been done quite
delibrately. kernel-package does not track these versions, and tries
to be kernel version agnostic, as far as possible. And I am not going
to have the kernel-package start tracking these requirements, it is
not going to be practical. kernel-package is not a substitute for
reading kernel documentation ;-). Before making a kernel image
package, one should look into Documentation/Changes and see that one
has the minimal requirements mentioned there. kernel-package does not
have any knowledge of what is in the kernel, and it should not, since
it can then work on all kinds of kernels with no modification.
Indeed, this is somewhat of a public service -- lack of module
init tools have induced people to read the CHANGES file, and mayhap
discover other critical information ;-) People should not be
compiling kernels without reading the docs. Especially new
major/minor version upgrade kernels. And always have a way to boot
your system.
This is not without precedent; we never depended on bin86, or
deprecated new versions of gcc, or anything like that. We are not
going to start tracking per version dependencies.
I am closing this report, since adding dependencies would make
kernel-package less useful.
manoj
--
Neil Armstrong tripped.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
