From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin: how to mount linux FS from cygwin
Date: Fri, 26 Oct 2018 16:38:00 -0000 [thread overview]
Message-ID: <7e2bad7d-0882-900e-2074-90996eaf38b1@gmail.com> (raw)
In-Reply-To: <1540569794858-0.post@n5.nabble.com>
Am 26.10.2018 um 18:03 schrieb hauck.adrian451:
> Thank you,
>
> I execute:
> - ninja
> - ninja install
>
>
> user@cliente ~/sshfs-sshfs-3.5.0/build
> $ ninja
> [5/6] Compiling C object 'sshfs@exe/sshfs.c.o'.
> ../sshfs.c: En la función âsshfs_initâ:
> ../sshfs.c:1746:28: aviso: â~â on a boolean expression [-Wbool-operation]
> cfg->nullpath_ok = ~(sshfs.truncate_workaround ||
> sshfs.fstat_workaround);
> ...
> [6/6] Linking target sshfs.exe.
>
> user@cliente ~/sshfs-sshfs-3.5.0/build
> $ ninja install
> [0/1] Installing files.
> Installing sshfs.exe to /usr/local/bin
> Running custom install script
> '/home/user/sshfs-sshfs-3.5.0/utils/install_helper.sh sbin bin'
> '/usr/local/sbin/mount.sshfs' -> '../bin/sshfs'
> '/usr/local/sbin/mount.fuse.sshfs' -> '../bin/sshfs'
>
> user@cliente ~/sshfs-sshfs-3.5.0/build
> $ sshfs
> cygfuse: initialization failed: winfsp-x64.dll not found
>
> and now respond the command but the error is "cygfuse: initialization
> failed: winfsp-x64.dll not found"
>
> has happened?
>
> Regards,
>
have you installed WinFSP ?
http://www.secfs.net/winfsp/download/
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-10-26 16:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 18:01 ping
2012-06-28 18:20 ` K Stahl
2012-06-28 19:35 ` ping
2012-06-28 19:56 ` Daniel Colascione
2012-06-28 20:09 ` Jeremy Bopp
2012-06-28 20:40 ` ping
2012-06-28 20:57 ` ping
2012-06-28 21:35 ` Andrey Repin
2012-06-29 8:17 ` Thorsten Kampe
2012-06-29 13:32 ` ping
2012-07-11 14:23 ` ping
2012-07-11 14:30 ` Christopher Faylor
2018-10-26 11:28 ` hauck.adrian451
2018-10-26 13:06 ` cyg Simple
2018-10-26 16:03 ` hauck.adrian451
2018-10-26 16:38 ` Marco Atzeri [this message]
2018-10-26 22:55 ` hauck.adrian451
2018-10-26 23:54 ` hauck.adrian451
2018-10-27 3:46 ` Brian Inglis
2018-10-28 1:32 ` hauck.adrian451
2018-10-28 21:27 ` Marco Atzeri
2018-10-28 21:54 ` René Berber
2018-10-29 4:36 ` Brian Inglis
2012-08-09 13:56 Tom Schutter
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=7e2bad7d-0882-900e-2074-90996eaf38b1@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).