mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pragnesh Sampat <pragnesh.sampat@timesys.com>
To: dank@kegel.com
Cc: hollisb@us.ibm.com, christopher.faylor@timesys.com, "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 15:27:38 -0400	[thread overview]
Message-ID: <1090524458.8679.23.camel@pss-pc.timesys> (raw)
In-Reply-To: <3D848382FB72E249812901444C6BDB1D036EDF21@exchange.timesys.com>

> > 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,

We have some patches that we use at TimeSys that allow a linux kernel to
build on cygwin.  They fall under:

1. case insensitive issues
2. kconfig using shared library
3. header file issues under some cygwin versions (typically types.h)
4. arguments handling limited to 32K (large number of modules are issues
in Makefiles)

1 and 2 have already been discussed and Chris Faylor mentioned just a
while ago that with managed mounts under newer cygwin versions, this is
not a big issue for cygwin at least.

Sometime later today, I will send in the patches we are using for 2.6.6
that allow a full build, in case they are useful (at least the arguments
handling patch is a kludge, but I will send it in to start with).

-Pragnesh






       reply	other threads:[~2004-07-22 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D848382FB72E249812901444C6BDB1D036EDF21@exchange.timesys.com>
2004-07-22 19:27 ` Pragnesh Sampat [this message]
2004-07-22 22:11   ` Sam Ravnborg
2004-07-22 23:26     ` Pragnesh Sampat
2004-07-23  4:38       ` Pragnesh Sampat
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 14:47 ` case-sensitive file names during build Hollis Blanchard
2004-07-22 14:59   ` Dan Kegel

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=1090524458.8679.23.camel@pss-pc.timesys \
    --to=pragnesh.sampat@timesys.com \
    --cc=ahu@ds9a.nl \
    --cc=akpm@osdl.org \
    --cc=alexander.povolotsky@marconi.com \
    --cc=christopher.faylor@timesys.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=dank@kegel.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

all inboxes | Powered by JetHome®