Closed GoogleCodeExporter closed 8 years ago
I saw the EXACT error message you saw (and also probably have the same
configuration: PPC G4 running OS X
10.4.8)
I was running xcode 2.2. When I upgraded that to 2.4, the compile worked.
(Unfortunately, it's a gigabyte
download from Apple. It would be nice to figure out if there's a workaround for
2.2). I noticed 0.9 was released
but isn't available for download, so I tried compiling both 0.7 and 0.9 and
both compile fine now.
(Off topic: This may become a FAQ: What's the safe upgrade path? Can I just
replace the existing kernel module
in place and reboot?)
Original comment by paul.fre...@gmail.com
on 28 Jan 2007 at 11:21
paul.fredrickson: No, 0.1.9 (*not* 0.9) wasn't "released". Until it's available
for download, it isn't released. The
"upcoming release" message(s) on the mailing and other information in the Wiki
is all preliminary -- for
heads-up purposes -- until there is an actual binary release. Before the source
tree is tagged for the binary
release, it's more volatile too.
As for a safe upgrade path, it would be best to install the latest binary
release. If you want to keep up-to-date
with the bleeding edge changes in the source tree, you will have to figure what
you need to replace based on
what source was changed. Rules of thumb (I'm ignoring some dependencies here):
* If fusefs/*.[ch] are changed, you need to replace the kext
* If fusefs/mount/* are changed, you need to replace mount_fusefs
* If fusefs/load/* are changed, you need to replace load_fusefs
* If libfuse/*.patch are changed, you need to recompiled the user-space library
Original comment by si...@gmail.com
on 29 Jan 2007 at 4:27
You do need Xcode 2.4. I've added this requirement to the HOWTO so that others
don't trip over this.
Original comment by si...@gmail.com
on 29 Jan 2007 at 4:28
(Just ran into this problem myself.)
To deal with this under 2.2:
After failure on...
/usr/bin/gcc -E -P -x c -Wno-trigraphs \
/Users/bs/Documents/code/macfuse/fusefs/build/fusefs.build/Release/fusefs.build/
Info.plist \
-o
/Users/bs/Documents/code/macfuse/fusefs/build/Release/fusefs.kext/Contents/Info.
plist
... you can cd to the relevant directory and rerun the command with an
additional "-I." switch. Running "port
install fusefs" a second time will now work.
I'm not an Xcode guy, but I bet it's easy to add this switch to the project...
Original comment by rbour...@gmail.com
on 7 May 2007 at 1:06
Original issue reported on code.google.com by
brandon....@gmail.com
on 24 Jan 2007 at 7:37