Frédéric BOITEUX wrote: >> * the modules which are autobuilt are for 2.6 only, etch will likely >>not ship any 2.4 kernel, so 2.4 autobuilt support would be useless anyway. > > mmm. But Etch isn't to be released soon ;-)
So you are seriously suggesting to hack a crapped 2.4 support in it although that in about 4-5 month, the base system is freezed for etch? Hm, I don't think this is worthy when we have m-a to semi-autobuild the modules in a sane way anyway. >> * if you still want to built modules for 2.4, you can semi-autobuild >>them by using module-assistant (therefore, it has the "squashfs-source" >>package). > > What I don't understand well is : did you modify the squashfs sources to be > able to build the module out of tree, or is it the 2.6.15 kernel which let you > do it ? That has nothing to do with 2.6.15, the problem is that upstream provides just patches, so I had to unpack them, fix the include definitions (debian/patches/01-includes.dpatch) and set a variable (debian/patches/02-defaults.dpatch). > And do you think the same source (out of tree) could compile with a 2.4 > kernel ? yep (if one add a 2.4 specific patch containing the diff between 2.4 and 2.6). -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
