Compilation of Linux kernel takes about an hour.
Assuming you’re using recent kernel and usual hardware available on the market at that time.
Thank you for your attention.
Compilation of Linux kernel takes about an hour.
Assuming you’re using recent kernel and usual hardware available on the market at that time.
Thank you for your attention.
$ time make -j10 deb-pkg
[...]
real 37m50.646s
user 95m0.296s
sys 5m57.186s
And that’s assuming you do like I do, compile pretty much everything (as a module) AND compile the kernel with debug information, which adds quite a bit to the total time (building the resulting .5 gigabyte package alone after compilation takes several minutes). With a trimmed down kernel and no debug symbols, I suspect times less than 15 minutes should be easy to achieve.
Not true. Compiling the recent Linux kernel on up-to-date Atari hardware takes almost a day.
I wouldn’t call Atari usual hardware these days ;P
It takes much less for a tailored configuration (e.g. localmodconfig). You are using -j, right?
Yes I’m using -j option.
You know, I remember last winter, when I’ve been working in the university, and my laboratory wasn’t warm enough (actually, it was quite cold there), so I decided to distcc kernel at ~16 computers which would otherwise be just idle. Well, that reduced kernel compilation time to ~10 minutes, but didn’t warm the room up, unfortunately, even when I looped that for ever and added few `bzip2 /dev/null` pipelines at each machine.
Crap, I meant `bzip2 < /dev/urandom | gzip | unzip | bunzip2 > /dev/null`
Ever thought of compiling on multiple cores at once?
The K3ninho corollary: Fifteen minutes if your .config is optimised for your hardware.
(Even then, that’s old news. My best time is based on spinning rust, rather than silicon storage. Solid-State Disks chop the time needed for a generic kernel drastically. Even better than copying the git tree into shared memory or somehow ensuring that the files are in-memory in the file cache — but only because you don’t have to jump through those hoops to get it into RAM and because you don’t have a search-the-file-cache wait time.)
K3n.