Opened 13 years ago
Closed 13 years ago
#31160 closed defect (fixed)
Installing fuse4x and fuse4x-kext
Reported by: | GRMrGecko (Mr. Gecko) | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | anatol (Anatol Pomozov), GRMrGecko (Mr. Gecko) | |
Port: | fuse4x-kext |
Description
I am unable to install fuse4x and fuse4x-kext, the problem appears to be the same with posix_cred_t. I have read other people had problems with it due to llvm. I would not know how to change it to gcc or llvm gcc as I read it has to be done in the patch and I would expect something like a environment variable (CC="/usr/bin/gcc-4.2" or something similar to that).
I am trying to install NTFS-3G on Lion (Mac OS X 10.7) and this is required by it. I have completely removed the beta of MacFUSE and tried using MacPorts to install it, but it says it's only 32Bit and doesn't work with 64Bit (In a nutshell) and to use Fuse4x which doesn't compile and install. If there is a way to tell MacPorts to install the latest beta version of MacFUSE, I may be able to use it as I know a lot of other software requires it and it will work with NTFS-3G.
Thanks for any help.
Attachments (2)
Change History (14)
Changed 13 years ago by GRMrGecko (Mr. Gecko)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to dports@… |
---|---|
Port: | fuse4x-kext added |
I see you're building with clang, which should only happen by default on Xcode 4.2. Is that what version you have? If you had Xcode 4.1, you would have gotten llvm-gcc-4.2. Try that instead:
sudo port clean fuse4x-kext sudo port install fuse4x-kext configure.compiler=llvm-gcc-4.2
If that doesn't work, try gcc-4.2:
sudo port clean fuse4x-kext sudo port install fuse4x-kext configure.compiler=gcc-4.2
Let us know which, if any, works.
comment:2 Changed 13 years ago by drkp (Dan Ports)
Status: | new → assigned |
---|
I haven't tried it myself with Xcode 4.2, but I don't think there should be any problems with clang for fuse4x or fuse4x-kext. Certainly they can both be built with either llvm-gcc or clang on Xcode 4.1.
(There is a problem building fuse4x-framework with clang -- #31006 -- but that should be unrelated)
comment:3 Changed 13 years ago by anatol (Anatol Pomozov)
I believe this is the culprit
fuse4x-kext-0.8.11/fuse_internal.h:70:5: error: use of undeclared identifier 'posix_cred_t' [3]
that comes from here https://github.com/fuse4x/kext/blob/master/fuse_internal.h#L69
It sounds like you use macport on Lion (MAC_OS_X_VERSION_MIN_REQUIRED == 1070) with older version of SDK (10.6) where posix_cred_t type is not defined.
comment:5 Changed 13 years ago by GRMrGecko (Mr. Gecko)
It still happens with GCC-4.2.
Now before we continue, let me mention my crazy setup of the developer tools.
I installed Xcode4 and then on top of that, I installed Xcode3 as if I use Xcode4, I would be forced to develop for newer Macs only and I must have PPC support (even I have a PPC machine I develop for).
I do not know if my setup would miss up anything, but other things appears to compile especially after I replace the xcode build link with one which is in Xcode4. If I need to do the same with GCC and Clang, I can, I just need support for PPC.
Attaching new log.
comment:7 follow-up: 8 Changed 13 years ago by anatol (Anatol Pomozov)
Could you please check that this change fixes the issue? https://github.com/anatol/kext/commit/ed3bb7c201ec227c87ccdc6198ff7d1650b58f56 (just compile the project with your environment).
Is there any better way to define whether the project is compiled with SDK10.7 ?
comment:8 Changed 13 years ago by drkp (Dan Ports)
Replying to anatol.pomozov@…:
Could you please check that this change fixes the issue? https://github.com/anatol/kext/commit/ed3bb7c201ec227c87ccdc6198ff7d1650b58f56 (just compile the project with your environment).
Huh? That won't work, posix_cred_t is a typedef not a preprocessor definition.
comment:9 Changed 13 years ago by anatol (Anatol Pomozov)
Yeah, I realized it a few minutes after I posted the message. Sorry.
What about this change https://github.com/anatol/kext/commit/0574d22863c33c6d44ce39442e97e5c99cfa4a99
comment:10 Changed 13 years ago by GRMrGecko (Mr. Gecko)
Well the xcodebuild command returns BUILD SUCCEEDED and no errors and when building with Xcode itself, it does the same.
All I would need is to ether find out how to manually compile NTFS-3G with Fuse4x or wait for the update to go through to MacPorts so I can compile using it. I decided to go to MacPorts as when I manually configured NTFS-3G, it says automount will not work due to binaries not existing which obviously if your going to mount a NTFS device, you would want it automatically.
comment:11 Changed 13 years ago by anatol (Anatol Pomozov)
This bug should be fixed once patch provided in #31207 will be submitted to the repository.
comment:12 Changed 13 years ago by drkp (Dan Ports)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
main log