From: "Boerner, Brian" <bmb@pirus.com>
To: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Using BK under Cygwin
Date: Fri, 12 Oct 2001 10:45:25 -0400 [thread overview]
Message-ID: <200110121441.JAA12950@lists.linuxppc.org> (raw)
Has anyone been able to get bk to download the kernel sources under cygwin.
I get the following error, which makes sense:
==========================================================================
Sfio has detected a name conflict between
"include/linux/netfilter_ipv4/SCCS/s.i
pt_mark.h" and "include/linux/netfilter_ipv4/SCCS/s.ipt_MARK.h";
This usually happen when you transfer file from a case-sensitive file
system (e.g. Unix) to a case insensitive file system (e.g FAT, NTFS)
Please rename one of the file and retry (see also "bk helptool mv")
==========================================================================
write on fd gzip_in gunzip2fd: Broken pipe
socket2pipe: reader error 2
I tried running the mv command, but when I start the clone again I get the
same error. I'm pretty new to bk so I'm assuming there is a way around this.
We've been stuck on 2.4.1-pre10 for awhile now and I want to investigate
moving forward.
Thanks.
-bmb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-10-12 14:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200110121441.JAA12950@lists.linuxppc.org \
--to=bmb@pirus.com \
--cc=linuxppc-embedded@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;
as well as URLs for NNTP newsgroup(s).