From: Dan Kegel <dank@kegel.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: 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
Date: Sun, 17 Oct 2004 10:47:07 -0700 [thread overview]
Message-ID: <4172B01B.5080404@kegel.com> (raw)
In-Reply-To: <20041017182929.GA27637@mail.13thfloor.at>
Herbert Poetzl wrote:
>>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).
>
>
> fair enough, but Mac OS X doesn't require this (UFS
> is case sensititve, and probably no linux guy/gal uses
> HFS+), so IMHO it's 'just' Cygwin* folks here ...
MacOSX uses HFS+ by default. As a result, 99% of
people using MacOSX are going to use HFS+. I'm
a serious Linux developer, but if I owned a Mac,
I'd probably leave it set to HFS+, since I like
to keep my systems vanilla (it makes it easier to
pick up my stuff and use it on someone else's machine).
Thus it's not just Cygwin that's affected; this is
a real issue for MacOSX as commonly configured.
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next prev parent reply other threads:[~2004-10-17 18:43 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
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 [this message]
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=4172B01B.5080404@kegel.com \
--to=dank@kegel.com \
--cc=bertrand.marquis@sysgo.com \
--cc=herbert@13thfloor.at \
--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.