Re: Building on case-insensitive systems and systems where -shared doesn't work well

[Dan Kegel <dank@kegel.com>]

Herbert Poetzl wrote:
>>>>>Converting .S -> .s is useful for debugging - please don't cripple the
>>>>>kernel developers just because some filesystems are case-challenged.
>>>>
>>>>Does the debug tools rely on files named *.s then?
>>>>
>>>>There are today ~1400 files named *.S in the tree, but none named *.s.
>>>>So my idea was to do it like:
>>>>*.S => *.asm => *.o
>>>>But if this breaks some debugging tools I would like to know.
>>>
>>>*.asm is nonstanard naming.  If we have to support case-challenged
>>>filesystems, please ensure that the rest of the nonbroken world can
>>>continue as they have done for the last few decades and live happily
>>>unaffected by these problems.
>>
>>I still do not see how a kernel developer are affected by changing
>>the extension of an intermidiate file - please explain.
> 
> hmm, maybe because they expect the output of the
> preprocessed assembly code to have the prefix .s
> instead of .asm (see gcc man page and play with
> gcc -S)

The only .s/.S ambiguities that need resolving are intermediate files,
so fixing them should only require changing a few Makefile rules.
Let's wait and see what the patch looks like before we
argue about it; maybe it will be simple to make everybody
happy here (well, except those who hate the idea of
letting anyone compile Linux kernels on Cgywin or MacOSX).
- Dan


-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html