public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "hauck.adrian451" <hauck.adrian451@hideweb.xyz>
To: cygwin@cygwin.com
Subject: Re: cygwin: how to mount linux FS from cygwin
Date: Fri, 26 Oct 2018 11:28:00 -0000	[thread overview]
Message-ID: <1540553280760-0.post@n5.nabble.com> (raw)
In-Reply-To: <20120711143028.GA14112@ednor.casa.cgf.cx>

Hi,

I could install the sshfs in cygwin, but goes on wihout found:

user@cliente ~/sshfs-sshfs-3.5.0/build
$ meson --reconfigure
The Meson build system
Version: 0.48.1
Source dir: /home/mssg/sshfs-sshfs-3.5.0
Build dir: /home/mssg/sshfs-sshfs-3.5.0/build
Build type: native build
Project name: sshfs
Project version: 3.5.0
Native C compiler: cc (gcc 7.3.0 "cc (GCC) 7.3.0")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Message: Compiler warns about unused result even when casting to void
Program rst2man found: NO
Configuring config.h using configuration
Dependency fuse3 found: YES (cached)
Dependency glib-2.0 found: YES (cached)
Dependency gthread-2.0 found: YES (cached)
Message: rst2man not found, not building manual page.
Program utils/install_helper.sh found: YES
(/home/mssg/sshfs-sshfs-3.5.0/utils/install_helper.sh)
WARNING: Project targetting '>= 0.38' but tried to use feature introduced in
'0.40.0': build_by_default arg in custom_target
Build targets in project: 3
WARNING: Project specifies a minimum meson_version '>= 0.38' but uses
features which were added in newer versions:
 * 0.40.0: {'build_by_default arg in custom_target'}
Found ninja-1.8.2 at /usr/bin/ninja

mssg@ltmssg ~/sshfs-sshfs-3.5.0/build
$ sshfs
-bash: sshfs: no se encontró la orden


Can you help me?

Regards,



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

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

  reply	other threads:[~2018-10-26 11:28 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 [this message]
2018-10-26 13:06           ` cyg Simple
2018-10-26 16:03             ` hauck.adrian451
2018-10-26 16:38               ` Marco Atzeri
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=1540553280760-0.post@n5.nabble.com \
    --to=hauck.adrian451@hideweb.xyz \
    --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).