#18671 closed update (fixed)
Can macfuse be upgraded to 2.0.3.2?
| Reported by: | other@… | Owned by: | kballard (Lily Ballard) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ports@…, mf2k (Frank Schima), nerdling (Jeremy Lavergne), asbjorn@…, tonytung@…, list-ener@…, stefan.van.der.eijk@…, Damien@…, jabronson@…, dominik.krebs@…, box@…, macports@…, nemo@…, wdierkes@…, trudelle@…, deti@…, dieter@…, randalla@…, camilo.aguilar@…, macports@…, marcin.zalewski@…, scooper@…, ndg.shopping@…, jhbong84@…, ckthree@…, mroman@…, ben-macports@…, mail@…, danrashid@…, jon@…, andreas.wilm@…, christopher.andrey@…, permezel@…, spam0911@…, dark.panda+macports@…, arto.bendiken@…, nicos_pavlov@…, drkp (Dan Ports), alakazam@…, engstrom@…, carl@…, jbrownson@…, cimnine@…, macports@…, Markus.Ueberall@… | |
| Port: | macfuse |
Description
Wasn't sure if macfuse can be upraded to 2.0 along with the other ports that depend on it
Attachments (4)
Change History (79)
comment:1 Changed 15 years ago by raimue (Rainer Müller)
| Owner: | changed from macports-tickets@… to eridius@… |
|---|---|
| Port: | macfuse added |
comment:2 Changed 15 years ago by kballard (Lily Ballard)
comment:4 Changed 15 years ago by mf2k (Frank Schima)
| Summary: | Can macfuse be upgraded to 2.0(.3.2)? → Can macfuse be upgraded to 2.0.3.2? |
|---|---|
| Type: | enhancement → update |
comment:6 follow-up: 10 Changed 15 years ago by nerdling (Jeremy Lavergne)
| Cc: | snc@… added |
|---|
Version 2.0.3.2's build tool tries to use OS 10.6 SDKs. This version cannot be updated until 10.6 is officially out.
Perhaps 2.0.3[.1] can be implemented instead?
comment:8 Changed 15 years ago by asbjorn@…
As can be seen in #20304, I'd love to have updated fuse libraries as well!
comment:10 Changed 15 years ago by tobypeterson
Replying to snc@…:
Version 2.0.3.2's build tool tries to use OS 10.6 SDKs. This version cannot be updated until 10.6 is officially out.
Ports should not be using any SDK, 10.6 or otherwise. Unless you mean it's trying to use new API...
comment:14 Changed 15 years ago by Damien@…
I have a problem with the macfuse. I need it to be active for installing the port sshfs. But at the same time I need macfuse 2.x for TrueCrypt.
So I did installed macfuse directly from the Google code repository, but there is no way I can tell MacPort that there is already a version installed.
Correctly, installing sshfs from macport pulls the macfuse port, which cannot be installed because there is already a kernel module present (from the Google code installation)
So I would need one of the two following solutions :
1) a way to tell the macfuse port to be installed, without writing the kernel module on the disk (which is outside the MacPort disk tree),
2) a way to tell the sshfs port not to pull macfuse.
Any preference?
comment:16 Changed 15 years ago by nerdling (Jeremy Lavergne)
I'm attempting to update this today. I'll let you know if it's successful.
Presently, I've got it using the 2.0.3.2 tag on svn.
Changed 15 years ago by nerdling (Jeremy Lavergne)
| Attachment: | macfuse.diff added |
|---|
comment:17 Changed 15 years ago by nerdling (Jeremy Lavergne)
I've got it functioning up through configure.
I'm not sure why the build script fails to get the compiler to function correctly.
I've uploaded an archive of the 2.0.3 tag to svn (it'll get to distfiles eventually).
comment:33 Changed 15 years ago by camilo.aguilar@…
Replying to camilo.aguilar@…:
Cc Me!
any updates ????, I need install ext2fuse an sshfs, but I get "Unsupported Mac OS X release 10.0.0" message when macfuse is beginning to compile
Regards,
Camilo
comment:47 Changed 14 years ago by info@…
For a newbie:
Any pointers on how to use the patch? Do I only have to patch build_macfuse.sh, or do I have to fetch some different source files from somewhere (and where would that be, where would I put them, etc)?
Thanks!
Changed 14 years ago by jlucg@…
| Attachment: | macfuse_fix_jlucg_buildonly_v1.tar.bz2_split1of2 added |
|---|
Fix to build macfuse 2.0.3 on Snow Leopard, part 1 of 2 (not tested, not for normal users)
Changed 14 years ago by jlucg@…
| Attachment: | macfuse_fix_jlucg_buildonly_v1.tar.bz2_split2of2 added |
|---|
Fix to build macfuse 2.0.3 on Snow Leopard, part 2 of 2 (not tested, not for normal users)
comment:50 Changed 14 years ago by jlucg@…
I have managed to get macfuse 2.0.3 to build on Snow Leopard. If you open the attached tarball and follow the instructions in the included README.txt, you should be able to get it to build on your system.
You will not yet be able to install the port as this part has not been fixed yet.
I have NOT tested the generated binary in any way. I need to give some of the fixes to the upstream maintainer of macfuse as they allow to build macfuse on Snow Leopard which was not possible the last time I checked (but Leopard-built macfuse would however work on Snow Leopard).
The tarball is split in two to be allowed to upload it to the site. To extract i t, just run:
cat macfuse_fix_jlucg_buildonly_v1.tar.bz2_split1of2 macfuse_fix_jlucg_buildonly_v1.tar.bz2_split2of2 | tar xvj
I don't have much time to work on this and I hope that somebody will be able to finish the work.
comment:55 Changed 14 years ago by panayotis@…
Replying to other@…:
Wasn't sure if macfuse can be upraded to 2.0 along with the other ports that depend on it
comment:56 Changed 14 years ago by panayotis@…
I know that this is an open source project and is based entirely on the free effort of people, but are there any updates when macfuse will be upgraded to 2.0? Thank you in any case for all your efforts :)
comment:64 follow-up: 65 Changed 14 years ago by deti@…
macfuse_fix_jlucg_buildonly_v1.tar.bz2 builds for me. Why not finishing the patch? Anyone?
comment:65 Changed 14 years ago by drkp (Dan Ports)
Replying to deti@…:
macfuse_fix_jlucg_buildonly_v1.tar.bz2 builds for me. Why not finishing the patch? Anyone?
It builds for me too, but I wasn't able to actually get it to work. (Does it work for you?)
I've only taken a very cursory look at it, so it is entirely possible that the fix is trivial or even that I'm just not testing it correctly. I hope to take another look at it soon, maybe this weekend.
comment:67 Changed 14 years ago by drkp (Dan Ports)
I've been working on packaging this up. It is considerably more painful and slow-going than I expected because the build system is fairly complicated and changed substantially since macfuse 1.x.
Just wanted people to point out that this isn't going ignored; hopefully I'll have a patch soon.
comment:71 Changed 14 years ago by drkp (Dan Ports)
OK, here is my first take at a complete portfile patch for MacFuse 2.0.
Contents
This applies a few new patches:
- files/patch-10.5-to-10.6.diff
- files/patch-macfuse_buildtool.sh.diff
- files/patch-sdk-objc_GMUserFileSystem.m.diff
- files/patch-sdk-objc_MacFuse.xcodeproj.diff
These four patch MacFUSE for 10.6 support -- the credit for these go to Jean-Luc Giraud, who did the bulk of the work. These patches should eventually be applied upstream. (Jean-Luc, have you submitted your changes to them?)
files/patch-sdk-objc_MacFuse.xcodeproj.diff also patches it to build in ${workpath} instead of /tmp.
- files/patch-10.4_libfuse_fuse-2.7.3-macosx.patch.diff
- files/patch-10.5_libfuse_fuse-2.7.3-macosx.patch.diff
- files/patch-10.6_libfuse_fuse-2.7.3-macosx.patch.diff
These three (which are essentially the same path) are specific to MacPorts, and cause it to install into ${destpath} during build, making a separate destroot phase unnecessary.
Testing
I have tested these (using sshfs) on 32-bit 10.6. I expect that it should still work on 10.4 and 10.5 as well, but would appreciate it if someone with a 10.4 or 10.5 system handy could test it.
I have not tested this on 64-bit yet and don't know what to expect. My guess is that the user-level libraries should build and work fine regardless of whether +universal is specified, but that the kernel module will only build 32-bit. According to this post, MacFUSE does not yet support 64-bit kernels. Feedback from anyone who tries this on 64-bit is especially appreciated; otherwise I'll see if I can borrow a 64-bit machine sometime soon.
Changed 14 years ago by drkp (Dan Ports)
| Attachment: | patch-macfuse-2.0.diff added |
|---|
Portfile and patches for MacFUSE 2.0
comment:72 Changed 14 years ago by mf2k (Frank Schima)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Version: | 1.7.0 |
r61907. Thanks! I will test it over the next few days.
In the future, please use a unified diff. I had to modify your patchfile in order to apply it because I didn't have the directory "/Users/dan/localports/fuse/macfuse".
comment:73 Changed 14 years ago by Markus.Ueberall@…
Let me be the first of all those who subscribed to this ticket to say:
Thank. You. So. Much.
IMHO, this is one of the most important ports.
comment:74 Changed 14 years ago by drkp (Dan Ports)
Appears that this doesn't build under 10.5. I'm looking into it now; moved to ticket #23007 in the interests of not gratuitously spamming everyone on the cc list for this one.
comment:75 Changed 13 years ago by anatol (Anatol Pomozov)
Hi, everyone.
I just want to let you know that macfuse has finally moved out of googlecode. The new project's home is https://github.com/macfuse
I am trying to apply macports patches to macfuse and submit it to the new git repo.
Feel free to fork the project, hack it and send your contribution back to macfuse.
Sure would be nice, 2.0 changed the build system pretty significantly. I haven't had the time to rewrite the Portfile for the new build system.