kernel 2.6.17 build from source fails

[Joel Bryan Juliano]

On 3/14/07, golfer <golfbuf at gmail.com> wrote:
> On 3/13/07, Joel Bryan Juliano <joelbryan.juliano at gmail.com> wrote:
> > Why not just use the 'make' method?
>
> My modem driver seems broken by kernel 2.6.20 (feisty), so I am trying
> to generate a package of the 2.6.17-generic from edgy and it's
> kernel-headers, that I can use on feisty when I want to use the modem.
>  It seemed easiest to just use the dpkg-buildpackage command.  But, I
> didn't realize it would take ~7 Gb.  So, I'll try it your suggestion
> instead.
>
> thanks,
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

Yes, because when you dpkg-buildpackage, you are building all the
kernels that is defined in the debian/control file.

For example for -generic, you will have to compile the -generic-debug,
-server-generic, -generic modules, and each of those are recompiling
the entire kernel to create 1 entry. That doesn't include the -386.

~7Gb is a bit small for the entire kernel, considering there's AMD,
PS3, 64-Bit, Sparc, etc, and a whole lot of different architecture
that you need to build,

The most sane way to dpkg-buildpackage operation for kernel is to have
a build-farm with huge storage and multiple processors.