Messages in this thread | | | Date | Tue, 11 Jun 2002 14:01:22 +0100 | From | Russell King <> | Subject | Re: 2.5.21: kbuild changes broke filenames with commas |
| |
On Tue, Jun 11, 2002 at 06:16:10AM -0600, Thunder from the hill wrote: > Well the question is then how will things look without commas? I suppose > if we have very complex things and prevent using commas whereas I don't > assert that we do for text but this is just a bloat example it's good to > have things like commas allowed even though we are in case we won't allow > them there talking about file names. > > If we allow commas all over the filesystem and likewise say that there is > nothing to mention about it why should we refuse them for kbuild > especially since there is a parallel system which allows commas?
You've *completely* missed the point.
The gcc argument >>> -Wp,-MD,foo,bar.c <<< is the problem. If anything should be fixed, its that silly gcc syntax. kbuild should not work around the inability of gcc to accept filenames with commas in.
-- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |