From: Russell King <rmk+lkml@arm.linux.org.uk>
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 20:06:27 +0100 [thread overview]
Message-ID: <20041016200627.A20488@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20041016210024.GB8306@mars.ravnborg.org>; from sam@ravnborg.org on Sat, Oct 16, 2004 at 11:00:24PM +0200
On Sat, Oct 16, 2004 at 11:00:24PM +0200, Sam Ravnborg wrote:
> On Wed, Oct 06, 2004 at 10:57:29PM -0700, Dan Kegel wrote:
> > Sam Ravnborg wrote:
> > >On Tue, Sep 21, 2004 at 10:40:24PM -0700, Dan Kegel wrote:
> > >> 683 2328 27265 linux-2.6.8-build_on_case_insensitive_fs-1.patch
> > >> 28 122 1028 linux-2.6.8-noshared-kconfig.patch
> > >
> > >Can you please post these two patches.
> > >The fist I hope is very small today.
> >
> > OK, here they are, plus a third one that also seems neccessary:
> >
> > This one's by Martin Schaffner:
> > http://www.kegel.com/crosstool/crosstool-0.28-rc37/patches/linux-2.6.8/linux-2.6.8-build_on_case_insensitive_fs.patch
> >
> Most of this is done in current linus-BK. I'm planning to handle
> asm-offset in another way and will then start to get rid of .S -> .s
Converting .S -> .s is useful for debugging - please don't cripple the
kernel developers just because some filesystems are case-challenged.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-10-16 19:06 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 [this message]
2004-10-16 21:24 ` Sam Ravnborg
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=20041016200627.A20488@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bertrand.marquis@sysgo.com \
--cc=dank@kegel.com \
--cc=kjh@hilman.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.