From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: sam@ravnborg.org, dank@kegel.com
Subject: Re: Building on case-insensitive systems
Date: 17 Oct 2004 01:06:14 -0400 [thread overview]
Message-ID: <1097989574.2674.14246.camel@cube> (raw)
> 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
The logic is sound, but... yuck!
> 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 oftenb ound to Windoze boxes - for
> different reasons. And the individual developer may not be able
> to change this.
The difficulty in building on a case-insensitive filesystem may
be the only hope these developers have for escaping Windows.
You turn "we must have Linux build systems to build our product"
into the less effective "we want Linux".
For the sake of these suffering developers, it would be better
to make sure that building Linux on Windows is a lost cause.
We could name a file "con" or "a:foo" for example.
next reply other threads:[~2004-10-17 5:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 5:06 Albert Cahalan [this message]
2004-10-17 4:38 ` Building on case-insensitive systems Dan Kegel
2004-10-17 5:43 ` Albert Cahalan
2004-10-17 9:27 ` Sam Ravnborg
2004-10-17 9:05 ` Anand Kumria
2004-10-17 16:41 ` Denis Vlasenko
2004-10-17 17:55 ` Albert Cahalan
2004-10-17 17:16 ` Dan Kegel
2004-10-17 19:54 ` Albert Cahalan
2004-10-17 19:34 ` Dan Kegel
[not found] <fa.e78dm07.jjs3q5@ifi.uio.no>
[not found] ` <fa.e17vks0.10kojhi@ifi.uio.no>
2004-10-17 12:19 ` Bodo Eggert
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=1097989574.2674.14246.camel@cube \
--to=albert@users.sf.net \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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