Hi there,

Go-FUSE doesn't work on MacOS; there are some small details with how
connection and datatypes are setup. If you want to fix that, feel free;
you can. See for some examples of how to setup the connection and the
datatypes.

http://code.google.com/p/rsc/source/browse/#hg%2Ffuse

you can find the corresponding code in fuse/mount.go and datatypes in raw/

On Sat, Sep 8, 2012 at 6:40 PM, Thomas Keller [email protected]:

Hi!

I'm trying to compile go-mtpfs on OSX 10.8, but this is failing because
the splice() syscall seems to be unavailable on the BSDs and some
constants are not available either:

github.com/hanwen/go-fuse/raw

src/github.com/hanwen/go-fuse/raw/print.go:56 http://github.com/hanwen/go-fuse/rawsrc/github.com/hanwen/go-fuse/raw/print.go:56: undefined: syscall.O_DIRECT
src/github.com/hanwen/go-fuse/raw/print.go:58: undefined: syscall.O_LARGEFILE
src/github.com/hanwen/go-fuse/raw/print.go:59: undefined: syscall.O_NOATIME

github.com/hanwen/go-fuse/splice

src/github.com/hanwen/go-fuse/splice/pair.go:68 http://github.com/hanwen/go-fuse/splicesrc/github.com/hanwen/go-fuse/splice/pair.go:68: undefined: syscall.Splice
src/github.com/hanwen/go-fuse/splice/pair.go:78: undefined: syscall.Splice
src/github.com/hanwen/go-fuse/splice/pair.go:86: undefined: syscall.Splice

Being not at all familiar with low-level C programming and Go I was
wondering if you could help me out resolving these issues?

From what I've read splice could be replaced by POSIX' memmap (
http://stackoverflow.com/questions/10329505), but I don't understand the
logic here...

On BSD's open(2) man page I read about the available open flags:

   O_RDONLY        open for reading only
   O_WRONLY        open for writing only
   O_RDWR          open for reading and writing
   O_NONBLOCK      do not block on open or for data to become available
   O_APPEND        append on each write
   O_CREAT         create file if it does not exist
   O_TRUNC         truncate size to 0
   O_EXCL          error if O_CREAT and the file exists
   O_SHLOCK        atomically obtain a shared lock
   O_EXLOCK        atomically obtain an exclusive lock
   O_NOFOLLOW      do not follow symlinks
   O_SYMLINK       allow open of symlinks
   O_EVTONLY       descriptor requested for event notifications only
   O_CLOEXEC       mark as close-on-exec

I also read the Linux open(2) man page and it still has to occur to me if
these Linux-specific flags that are used in go-mtpfs are really, really
needed, but hey, you're the expert :)

Thanks,
Thomas.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11.

Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen

from go-mtpfs.

Closed: Won't fix or Closed: Implemented?

from go-mtpfs.

Closed: this is a go-fuse issue (https://github.com/hanwen/go-fuse)

On Wed, Jan 9, 2013 at 12:21 PM, Thomas Keller [email protected]:

Closed: Won't fix or Closed: Implemented?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-12040205.

Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen

from go-mtpfs.

Unfortunately there is no issue tracker available in this project. Could you please enable it? Then I could migrate this issue to the proper project.

from go-mtpfs.

Done.

On Wed, Jan 9, 2013 at 12:22 PM, Han-Wen Nienhuys [email protected] wrote:

Closed: this is a go-fuse issue (https://github.com/hanwen/go-fuse)

On Wed, Jan 9, 2013 at 12:21 PM, Thomas Keller [email protected]:

Closed: Won't fix or Closed: Implemented?

Han-Wen Nienhuys - [email protected] - http://www.xs4all.nl/~hanwen

from go-mtpfs.