> > Please don't do that. > > If you simply define -D__DARWIN_INO_64_T=1, recompile libfuse, > overwrite MacFUSE's libfuse, and have *your* file system working to > your satisfaction, what about other MacFUSE file systems? When you > define that flag, both the size and layout of the stat structure > change. Every MacFUSE file system binary except yours will break. Are > you sure that none of your users will ever use another MacFUSE file > system binary from another source? If they do, not only will it fail > 100% of the time, the failure is likely to be mysterious and > frustrating to users and developers alike. >
I understand this problem. But had not seen no other option to use 64 bit libfuse with GlusterFS on MacOSX otherwise. > > If 64-bit inode number reporting is a must for you, do the following > instead. > Make sure (obviously) that your own file system code is compiled with - > D__DARWIN_64_BIT_INO_T=1 and then link against libfuse_ino64 rather > than libfuse: that is, do '-lfuse_ino64' instead of '-lfuse'. You'll > need the latest Developer Release (1.9.35+) to be able to do so. > Thanks for this info, this is completely doable and I can handle this in configure time. Btw, where can I get developer release (mainly 1.9.35+??) I got MacFuse-1.9.dmg earlier from 'DeveloperRelease.plist' in the source tree. Is it same as http://macfuse.googlecode.com/svn/releases/developer/MacFUSE-1.9.dmg ? Regards, Amar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
