Re: Building on case-insensitive systems and systems where -shared doesn't work well (was: Re: 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)?)

From: Herbert Poetzl
Date: Sun Oct 17 2004 - 12:00:23 EST


On Sun, Oct 17, 2004 at 12:04:27AM +0200, Sam Ravnborg wrote:
> On Sat, Oct 16, 2004 at 08:40:01PM +0100, Russell King wrote:
> > On Sat, Oct 16, 2004 at 11:24:40PM +0200, Sam Ravnborg wrote:
> > > On Sat, Oct 16, 2004 at 08:06:27PM +0100, Russell King 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)

GCC(1) GNU Tools GCC(1)

.s Assembler source; assemble
.S Assembler source; preprocess, assemble

best,
Herbert

>
> Sam
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/