Conversation
|
I don't see what the motivation for adding Linux 2.6.16 is. There is no reason to want it to match the kernel version used on the host you're compiling on (these things have nothing to do with each other) and an ancient kernel like that is just more likely to have headers that clash with userspace use or have other bugs. We should really avoid adding more kernel versions unless they're known to provide headers with better compatibility than the versions we already have. For tar, I think it's welcome to support tar versions without the J option, but I think this patch is also likely to break building on systems that don't have the xz command installed. I think a patch that made either setup work would be acceptable though. |
|
Okay, I'll work on a patch that would support both. For xz, it would break the case where tar is from libarchive, since gnu tar needs xz to work even with support. The motivation is to create a toolchain that targets CentOS 5. |
|
In "The motivation is to create a toolchain that targets CentOS 5", do you mean motivation for using old kernel headers? This is not necessary. New kernel headers work perfectly fine for producing programs to run on an old kernel. |
Simple changes to build on CentOS 5.