From: Padraig@Linux.ie
To: Larry McVoy <lm@bitmover.com>
Cc: Steve Kenton <skenton@ou.edu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [FYI} The cygwin tool chain can *almost* build a 2.5.59 kernel
Date: Mon, 27 Jan 2003 17:32:39 +0000 [thread overview]
Message-ID: <3E356D37.2000304@Linux.ie> (raw)
In-Reply-To: <20030127171308.GA24651@work.bitmover.com>
Larry McVoy wrote:
> Last I checked the kernel has file name conflicts, i.e., "README" and
> "Readme" in the same directory in a windoze based file system. You may
> not notice it if you get your kernel with tar but if you get it with BK
> then BK will detect that and tell you about it. I don't remember which
> files conflict but I know there are about 12 of them in the 2.5 kernel.
The findsn component of http://www.pixelbeat.org/fslint/
shows the following (24 files) for 2.5.59:
include/linux/netfilter_ipv4/ipt_dscp.h
include/linux/netfilter_ipv4/ipt_DSCP.h
include/linux/netfilter_ipv4/ipt_ecn.h
include/linux/netfilter_ipv4/ipt_ECN.h
include/linux/netfilter_ipv4/ipt_mark.h
include/linux/netfilter_ipv4/ipt_MARK.h
include/linux/netfilter_ipv4/ipt_tcpmss.h
include/linux/netfilter_ipv4/ipt_TCPMSS.h
include/linux/netfilter_ipv4/ipt_tos.h
include/linux/netfilter_ipv4/ipt_TOS.h
include/linux/netfilter_ipv6/ip6t_mark.h
include/linux/netfilter_ipv6/ip6t_MARK.h
net/ipv4/netfilter/ipt_dscp.c
net/ipv4/netfilter/ipt_DSCP.c
net/ipv4/netfilter/ipt_ecn.c
net/ipv4/netfilter/ipt_ECN.c
net/ipv4/netfilter/ipt_mark.c
net/ipv4/netfilter/ipt_MARK.c
net/ipv4/netfilter/ipt_tcpmss.c
net/ipv4/netfilter/ipt_TCPMSS.c
net/ipv4/netfilter/ipt_tos.c
net/ipv4/netfilter/ipt_TOS.c
net/ipv6/netfilter/ip6t_mark.c
net/ipv6/netfilter/ip6t_MARK.c
Pádraig.
prev parent reply other threads:[~2003-01-27 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 17:00 [FYI} The cygwin tool chain can *almost* build a 2.5.59 kernel Steve Kenton
2003-01-27 17:13 ` Larry McVoy
2003-01-27 17:32 ` Padraig [this message]
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=3E356D37.2000304@Linux.ie \
--to=padraig@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=skenton@ou.edu \
/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