From: Dan Kegel <dank@kegel.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>,
crossgcc <crossgcc@sources.redhat.com>,
"'linuxppc-dev@lists.linuxppc.org'"
<linuxppc-dev@lists.linuxppc.org>,
"'Andrew Morton'" <akpm@osdl.org>, "'bert hubert'" <ahu@ds9a.nl>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: case-sensitive file names during build
Date: Thu, 22 Jul 2004 07:59:23 -0700 [thread overview]
Message-ID: <40FFD64B.8040304@kegel.com> (raw)
In-Reply-To: <0C006758-DBEE-11D8-9AB1-000A95A0560C@us.ibm.com>
Hollis Blanchard wrote:
> On Jul 22, 2004, at 4:25 AM, Povolotsky, Alexander wrote:
>>> make[3]: *** No rule to make target
>>> `net/ipv4/netfilter/ipt_ecn.o', needed by
>>> `net/ipv4/netfilter/built-in.o'.
>>> Stop.
>>
>> This is the (somewhat questionable) use of ipt_ECN.c and ipt_ecn.c in the
>> linux kernel. Windows filesystems are case insensitive, and see this
>> as one file.
>
> I had not seen the ECN/ecn problem, but you will also be bitten by .S ->
> .s preprocessing. That's right about the point that I gave up ...
I maintain patches that allow building glibc on Cygwin and MacOSX.
The main patch deals with exactly this issue (S vs. s)
http://kegel.com/crosstool/crosstool-0.28-rc26/patches/glibc-2.3.2/glibc-2.3.2-cygwin.patch
I have to maintain it separately as the glibc maintainer dislikes the
idea of catering to Cygwin users (though maybe if I present it
as a MacOSX support patch he'd reconsider... naaah, probably not :-).
With the advent of linux-2.6, I also have a patch
to get kconfig to not use shared libraries (since I use kconfig
to help install the kernel headers, and shared libraries are tricky
to build on those two platforms).
It wouldn't be a big leap for me or someone else to also maintain
a patch to allow compiling the whole kernel on Cygwin or MacOSX.
If anyone puts it together, I'll carry it in crosstool.
- Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next prev parent reply other threads:[~2004-07-22 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 9:25 (somewhat questionable) use of ipt_ECN.c and ipt_ecn.c in the linux kernel Povolotsky, Alexander
2004-07-22 11:09 ` Olaf Hering
2004-07-22 14:47 ` case-sensitive file names during build Hollis Blanchard
2004-07-22 14:59 ` Dan Kegel [this message]
[not found] <3D848382FB72E249812901444C6BDB1D036EDF21@exchange.timesys.com>
2004-07-22 19:27 ` Pragnesh Sampat
2004-07-22 22:11 ` Sam Ravnborg
2004-07-22 23:26 ` Pragnesh Sampat
2004-07-23 4:38 ` Pragnesh Sampat
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=40FFD64B.8040304@kegel.com \
--to=dank@kegel.com \
--cc=Alexander.Povolotsky@marconi.com \
--cc=ahu@ds9a.nl \
--cc=akpm@osdl.org \
--cc=crossgcc@sources.redhat.com \
--cc=hollisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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