%% [email protected] (Arthur Othieno) writes:
>> The patch will be included in 2.6.17 and will see exposure in -mm when
>> Andrew does next -mm.
ao> Sam, this was merged into Linus' tree post v2.6.16 (like you
ao> intended), but, won't the window between now and 2.6.17 be a
ao> little too big for such a fix? Debian etch (and sid) already ships
ao> with the affected make version:
ao> $ make -v | head -1
ao> GNU Make 3.81rc1
I reverted this fix in GNU make 3.81rc2 (available for a bit over a week
now). 3.81 final will ship with the old, buggy behavior instead of the
fixed behavior.
Immediately post-3.81 I'll re-introduce the GNU make fix.
Note that this only impacts people who build the kernel multiple times
without cleaning the tree. While this is very common with newer
versions of the kernel (for developers) it's probably less common with
older versions, and many of those (distro-based) can apply this kbuild
patch with the rest of their distro-specific patches.
On the gripping hand, it's quite possible to provide a significantly
smaller, targeted patch that fixes just the most egregious problem with
only two lines changed, if the -stable team was interested in that
instead.
--
-------------------------------------------------------------------------------
Paul D. Smith <[email protected]> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
