DSL Ideas and Suggestions :: dsl with kernel headers and development libraries

Quote

This should be the best solution because you'll get the same release of gcc-2.95 that dsl's kernel was compiled with. Modules are only ever supposed to be compiled with _exactly _ the same gcc version as was the kernel.

This is quite feasible on DSL, and juanito has even posted an extension for 2.95 in mydsl.

Quote

Unfortunately though, the contents of /usr/src on that knoppix are not always enough - in which case a 2.4.26 kernel source tree need to be prepared (begin a kernel recompile and quit early).

If./configure allows a pointer to the sources on the hd this is fine, otherwise I've tried editing the Makefile to point at same (doesn't always seem to work).

A problem with compiling from the livecd is that Knoppix 3.4's /usr tree is not writeable (no unionfs), so you can't symlink /usr/src/linux-2.4/.26 to your sources, which means /lib/modules/2.4.26/build is not linked to the sources either.

I have tried doing a mkwriteable type of thing on the /usr tree but ran out of ram ... a hd install of knoppix would be altogether easier.

You could try a symlink from /usr/src/linux to somewhere on a hdd, etc. But yes, it would be more elegant if you can use change it during configure time.

I thought someone might say that. More precicely: I'm not certain (?) that Janito's is the exact same release as the gcc-2.95 on knoppix 3.4 - the latter is some Debian-pre-release-blah blah version. They might indeed be the same. So, until, this is confirmed ...

Quote

symlink from /usr/src/linux to somewhere on a hdd

Err.. that's around the wrong way :=) You can't do:

Code Sample

ln -s /somewhere_on_hd/sources /usr/src/linux-2.4.26

You can't write a symlink to /usr/src. It ain't writeable. The other way around would need to clobber your sources.

original here.