On Sun, Mar 30, 2008 at 10:23 PM, Amit Singh <[EMAIL PROTECTED]> wrote: > > Try compiling the PowerPC version with EXT2FS_ENABLE_SWAPFS defined in > your CFLAGS.
Good idea. Actually, I discovered that the correct compile-line define is -DENABLE_SWAPFS. This simply triggers EXT2FS_ENABLE_SWAPFS, but looks as if ENABLE_SWAPFS is what the author intended to be the public macro. Regardless, EXT2FS_ENABLE_SWAPFS turns on code that detects whether byte swapping needs to occur. Thus, if you want to do an easy universal build, you can turn this on and the build will work identically on PPC and intel; the macro is only needed on PPC, though. For those wishing to replicate my experience, I used the following command line to invoke "configure" for ext2fuse: $ CFLAGS="-DENABLE_SWAPFS `pkg-config --cflags fuse` -arch i386 -arch ppc" LDFLAGS="-arch i386 -arch ppc" ./configure --prefix=/usr/local --disable-dependency-tracking I have experienced something odd so far in that, for the one ext3 filesystem I have available to play with, whenever I mount the filesystem using ext2fuse, the mount point ends up being owned root:wheel rather than as the user that ran ext2fuse. When I check the mount status using mount(1m), it correctly indicates that the filesystem was mounted by the non-root user. The mount point was even created by the same non-root user. Yet, ls -ld on the mount point (after mounting) has its ownership as root:wheel. I'll poke around more tomorrow, but if anybody's got ideas I should check out, drop me a line. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
