All: Should pvfs2fuse.c specify its include file for fuse with <fuse/fuse.h> or <fuse.h>?
In my environment, I installed fuse4x using "ports" which puts the fuse include directories in /opt/local/include/fuse with a compatibility file, fuse.h, in /opt/local/include. According to this compatibility file, fuse should be included with <fuse.h>. It also states that the include directories can be found using "pkg-config --cflags fuse", which generates the following: -D_FILE_OFFSET_BITS=64 -D_DARWIN_USE_64_BIT_INODE -I/opt/local/include/fuse The OFS config file uses the pkg-config command and thus uses the include directory /opt/local/include/fuse when pvfs2fuse.c is compiled. The current version of pvfs2fuse.c needs to be changed from <fuse/fuse.h> to <fuse.h> to accommodate the pkg-config command. I can easily make this change; however, I am not a MAC developer and want to know if this scenario is typical or just a result of using ports to install fuse? Any advice would be appreciated. Becky -- Becky Ligon OrangeFS Support and Development Omnibond Systems Anderson, South Carolina
_______________________________________________ Pvfs2-developers mailing list Pvfs2-developers@beowulf-underground.org http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
