From: Burt Silverman <burtms@gmail.com>
To: linhaifeng <haifeng.lin@huawei.com>
Cc: Jan Viktorin <viktorin@rehivetech.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
dev@dpdk.org
Subject: Re: test: failed to clone dpdk source in windows
Date: Mon, 8 Aug 2016 00:06:38 -0400 [thread overview]
Message-ID: <CAP0-SexGTPzBH4tJFDumbw8s85nnGshjkTeaEFSUE=7gzQdG7g@mail.gmail.com> (raw)
In-Reply-To: <57A80192.3050409@huawei.com>
Oddly enough, it seems to work fine under cygwin. That should solve your
issue.
On Sun, Aug 7, 2016 at 11:50 PM, linhaifeng <haifeng.lin@huawei.com> wrote:
> 在 2016/8/7 4:33, Jan Viktorin 写道:
> > On Fri, 05 Aug 2016 09:51:06 +0200
> > Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> >
> >> 2016-08-05 09:44, Thomas Monjalon:
> >>> 2016-08-05 10:09, linhaifeng:
> >>>> hi,thomas
> >>>>
> >>>> Could you change the name of file in directory
> app/test/test_pci_sysfs/bus/pci/devices/ ?
> >>>> I think somebody like us also cann't access internet in
> liunux.Windows not support file name
> >>>> include ':'.
> >
> > Hello,
> >
> > I am sorry for this situation but (as Thomas mentioned below) Windows is
> > not considered as a supported platform. If you have issues with this
> > approach you are welcome to prepare some patch changing this to do
> > the same thing in another way.
> >
> > There was a discussion when accepting the fake sysfs into DPDK on the
> > public mailing list. I did not received any serious complaints at that
> > time.
> >
> > Regards
> > Jan
> >
> >>>
> >>> Not sure to understand the use case.
> >>> This is a fake sysfs, we cannot change the names.
> >>
> >> In other words, Windows is not supported, neither for runtime
> >> nor for development.
> >> For information, which filesystem do not support ':'?
> >>
> >> If someone wants to add this support, the fake sysfs could have slightly
> >> different names and rightly renamed during compilation.
> >
>
> I just want to edit code in windows and compile in linux,so i want to
> clone it in windows,but
> it's not support.The message in win7 is :
> $ git clone http://dpdk.org/git/dpdk
> Cloning into 'dpdk'...
> remote: Counting objects: 51912, done.
> remote: Compressing objects: 100% (10331/10331), done.
> rRemote: Total 51912 (delta 41342), reused 51808 (delta 41eceiving
> objects: 100%
> (51271)912/519 MiB |
> Receiving objects: 100% (51912/51912), 25.99 MiB | 1.99 MiB/s, done.
> Resolving deltas: 100% (41342/41342), done.
> Checking connectivity... done.
> fatal: cannot create directory at 'app/test/test_pci_sysfs/bus/
> pci/devices/0000:
> 01:00.0': Invalid argument
> warning: Clone succeeded, but checkout failed.
> You can inspect what was checked out with 'git status'
> and retry the checkout with 'git checkout -f HEAD'
>
> If everyone edit codes in linux there is no need to fix it.
>
>
>
prev parent reply other threads:[~2016-08-08 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 2:09 test: failed to clone dpdk source in windows linhaifeng
2016-08-05 7:44 ` Thomas Monjalon
2016-08-05 7:51 ` Thomas Monjalon
2016-08-06 20:33 ` Jan Viktorin
2016-08-08 3:50 ` linhaifeng
2016-08-08 4:06 ` Burt Silverman [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='CAP0-SexGTPzBH4tJFDumbw8s85nnGshjkTeaEFSUE=7gzQdG7g@mail.gmail.com' \
--to=burtms@gmail.com \
--cc=dev@dpdk.org \
--cc=haifeng.lin@huawei.com \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.com \
/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).