From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Kegel <dank@kegel.com>, Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Martin Schaffner <schaffner@gmx.li>,
Kevin Hilman <kjh@hilman.org>,
bertrand marquis <bertrand.marquis@sysgo.com>
Subject: 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)?)
Date: Sat, 16 Oct 2004 23:24:40 +0200 [thread overview]
Message-ID: <20041016212440.GA8765@mars.ravnborg.org> (raw)
In-Reply-To: <20041016200627.A20488@flint.arm.linux.org.uk>
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.
Btw. this is not about "case-challenged" filesystems in general. This is
about making the kernel usefull out-of-the-box for the increasing
embedded market.
Less work-around patces needed the better. And these people are often
bound to Windoze boxes - for different reasons. And the individual
developer may not be able to change this.
Sam
next prev parent reply other threads:[~2004-10-16 19:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 6:03 2.6.8 link failure for sparc32 (vmlinux.lds.s: No such file or directory)? Dan Kegel
2004-09-21 10:50 ` Sam Ravnborg
2004-09-21 10:57 ` William Lee Irwin III
2004-09-22 5:40 ` Dan Kegel
2004-09-24 20:19 ` Sam Ravnborg
2004-10-07 5:57 ` 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)?) Dan Kegel
2004-10-16 21:00 ` Sam Ravnborg
2004-10-16 19:06 ` Russell King
2004-10-16 21:24 ` Sam Ravnborg [this message]
2004-10-16 19:40 ` Russell King
2004-10-16 19:04 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-16 22:04 ` 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)?) Sam Ravnborg
2004-10-17 16:57 ` Herbert Poetzl
2004-10-17 16:42 ` Building on case-insensitive systems and systems where -shared doesn't work well Dan Kegel
2004-10-17 18:29 ` Herbert Poetzl
2004-10-17 17:47 ` Dan Kegel
2004-10-17 19:06 ` Herbert Poetzl
2004-10-17 19:32 ` Dan Kegel
2004-10-31 21:10 ` 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)?) Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041016212440.GA8765@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bertrand.marquis@sysgo.com \
--cc=dank@kegel.com \
--cc=kjh@hilman.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schaffner@gmx.li \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox