On Fri, May 20, 2011 at 12:46 PM, David Boyce wrote:
> My company makes drivers. The corollary is that we keep dozens if not hundreds
> of entire Linux kernel source build trees going back 10 years or so in order
> to build drivers for them. The way Linux kernel drivers are built makes it
> necess
Follow-up Comment #6, bug #33034 (project make):
In fairness, this is a special situation. I have the same problem as "tz", and
I expect quite a few other people do too.
My company makes drivers. The corollary is that we keep dozens if not hundreds
of entire Linux kernel source build trees going
Follow-up Comment #5, bug #33034 (project make):
I'm not trying to be flip, but what do you do when you upgrade to a new
version of the compiler and older code no longer builds correctly due to more
stringent requirements? I see this in code all the time (not GNU make) with
new versions of GCC fo
Follow-up Comment #4, bug #33034 (project make):
It would help if for the next version there was a backward compatibility
switch - there are a lot of archived kernel source trees (and probably a lot
of other projects) that this breaks.
It would also help if the error message noted it was a change
