Enter one-line summary

[GoogleCodeExporter]

What steps will reproduce the problem?

1. download distribution at www.igorfs.org (ask me or admin there if you want a 
password, it's 
no problem)
2. unpack igor, cd igor, ./configure
3. unpack igorfs, cd igorfs, ./configure

What is the expected output? What do you see instead?

Expected output is that igorfs would pass configure, make, and make install. 
Instead it fails at 
the configure stage.

Igorfs is an experimental file system that we have tested on a range of 
linux/fuse combinations - 
thus far with success.

Using macfuse on Mac OSX we get an error (see output below). The error seems 
suggest that  
fuse.h requires a file called sys/statfs.h that does not seem to appear 
anywhere in the macfuse 
distribution.

This suggests that macfuse is missing an essential header file ('statfs.h').

--- config.log snip ---
configure:20612: checking for fstream
configure:20619: result: yes
configure:20642: checking fuse.h usability
configure:20654: g++ -c -g -O2 -I/usr/local/include conftest.cc >&5
In file included from /usr/local/include/fuse/fuse.h:619,
                 from /usr/local/include/fuse.h:9,
                 from conftest.cc:64:
/usr/local/include/fuse/fuse_compat.h:68:24: error: sys/statfs.h: No such file 
or directory
configure:20660: $? = 1
--- config.log snap ---

What version of the product are you using? On what operating system?

MacFUSE-Core-0.2.2.dmg on mac os x 10.4.8

Please provide any additional information below.

The main developer of igorfs suggested to me the following possible solutions:
 - it may be  easily to install a sys/statfs.h  that matches mac os (?)
 - tweak the fuse header file so it is happy
 - report the bug to macfuse development

Original issue reported on code.google.com by sean%odo...@gtempaccount.com on 2 Mar 2007 at 11:22

[GoogleCodeExporter]

Issue name should be "Macfuse is missing header file 'statfs.h'"

Original comment by sean%odo...@gtempaccount.com on 2 Mar 2007 at 11:25

[GoogleCodeExporter]

Reposting this on the macfuse-devel mailing list will get you a quicker and 
better answer, and will be more 
appropriate. This is not an issue with MacFUSE.

Original comment by si...@gmail.com on 2 Mar 2007 at 6:03

• Changed state: Invalid