This is a command that I use for testing your changes:

It assumes that 'pkg-config --libs fuse' works fine

$ git clone git://github.com/anatol/tup.git && cd tup && git checkout fuse && ./bootstrap.sh

It works with the latest official release (+macports patches) but fails with your master:

[ 0/17 ] src/tup/CC create_name_file.c
unique: 11, opcode: ACCESS (34), nodeid: 1, insize: 48
access / 01
unique: 11, success, outsize: 16
unique: 11, opcode: LOOKUP (1), nodeid: 1, insize: 46
LOOKUP /Users
getattr /Users
NODEID: 2
unique: 11, success, outsize: 152
unique: 12, opcode: FORGET (2), nodeid: 2, insize: 48
FORGET 2/1
DELETE: 2
Users/anatol/sources/tup: Invalid argument

I guess that something wrong with the DELETE.

Hi,

ok finally I created a reduced testcase that shows issues with macfuse+pthreads. macfuse works fine if fuse_loop() is in the main thread. But when we want to run it in a separate thread and access filesystem from another thread - we have issues.

The test case is at https://gist.github.com/976896 See the commends at the bottom of the file that briefly describe the issues.

It says "kextload" does not have -s parameter. I guess "kextutil -s" should be used in macfuse_buildtool.sh

But even with this change on my machine it fails with:

=== BUILD NATIVE TARGET fusefs OF PROJECT fusefs WITH CONFIGURATION Debug ===
Check dependencies

** BUILD SUCCEEDED **

MacFUSEBuildTool(reload) : reloading kext
Notice: Using running kernel architecture i386 to generate symbols.
Warnings:
Executable does not contain code for architecture:
i386

/tmp/fusefs.kext appears to be loadable (not including linkage for on-disk libraries).
Loading /tmp/fusefs.kext.
Can't load /tmp/fusefs.kext - no code for running kernel's architecture.
Failed to load /tmp/fusefs.kext - (libkern/kext) requested architecture/executable not found.
Failed to load /tmp/fusefs.kext - (libkern/kext) requested architecture/executable not found.
MacFUSEBuildTool(reload) failed: cannot load newly built MacFUSE kext.

void

Hi,

Here is a follow up for the issue #3. Testing my app with your master branch and there is yet another issue:

unique: 2, opcode: ACCESS (34), nodeid: 409, insize: 48
access /Users/anatol/sources/tup/@tupjob-28/libtup_client.a 02
unique: 2, success, outsize: 16
unique: 1, opcode: ACCESS (34), nodeid: 409, insize: 48
access /Users/anatol/sources/tup/@tupjob-28/libtup_client.a 00
unique: 1, success, outsize: 16
unique: 3, opcode: UNLINK (10), nodeid: 408, insize: 56
QUEUE PATH 409 (w)
WAIT ON PATH 409 (w)
/usr/bin/ranlib: can't create output file: libtup_client.a (Bad file descriptor)
ar: internal ranlib command failed

The "WAIT ON PATH" message comes from http://www.google.com/codesearch/p?hl=en#rdCCvgMofJA/trunk/rdp/fuse/fuse-2.8.4/lib/fuse.c&q=%22WAIT%20ON%20PATH%22&sa=N&cd=1&ct=rc&l=645

Here is the code that originally added the logic anatol/fuse@72faaa5

I am going to recompile 2.1.1 and see if it is reproducible on that version.

I try to run this command on 64bit kernel

$ ./macfuse_buildtool.sh -t examples

and it fails:
config.status: creating lib/Makefile
config.status: creating util/Makefile
config.status: creating include/Makefile
config.status: creating include/config.h
config.status: include/config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Can't open Makefile: No such file or directory.
MacFUSEBuildTool(examples) : running make
make: *** No targets specified and no makefile found. Stop.
MacFUSEBuildTool(examples) failed: make failed while compiling the MacFUSE examples.