libfuse@2: Linux is required for this software.

[aogg]

code@kingdeMacBook-Air ~ % brew install ext4fuse
Running brew update --auto-update... ext4fuse: Linux is required for this software. libfuse@2: Linux is required for this software. Error: ext4fuse: Unsatisfied requirements failed this build.

https://apple.stackexchange.com/questions/454827/installation-issue-ext4fuselinux-is-required-for-this-software-on-mac-os-moj

[aogg]

https://github.com/gerard/ext4fuse/issues/74

mac 11 big sur

[DavidInRacine]

74

Same here, but OS 10.14.6 Mojave.

Solutions posted in the apple.stackexchange link did not work for me.

I compiled ext4fuse source code, however I cannot get Apple's Security and Privacy — even following a reboot.

I am auditioning Paragon Software's commercial app, extFS, on a 10 day trial. If it works well maybe it's worth 40 USD? Alternatively one can use a linux VM, with the downsides of a VM.

[gustavopi]

Same here in Ventura 13.4.1

Also I needed to change ownership of a file inside Fuse before.

As long there is paid option and VM, this solution could be an alternative for those don't need or what to install whole VM or to pay 40 bucks...

[waytgibbs]

Same issue occurs in Ventura 13.5.1.

[tmladek]

+1, Ventura 13

[MisutaaAsriel]

Issue occurs on macOS Sonoma. Issue is because the application is listed as being for Linux, not macOS, in Brew: https://formulae.brew.sh/formula/ext4fuse

Essentially, it is published for the wrong platform. (This would be pointless on Linux as Linux has native extfs support).

[albertskog]

Did not try the workaround myself yet but see #66! It also gives some background, it's a licensing issue with macFuse..

[MisutaaAsriel]

Did not try the workaround myself yet but see #66! It also gives some background, it's a licensing issue with macFuse..

Not sure where you got that it was a licensing issue. Anyhow, I did the manual .rb install and that seemingly worked. It still stands that ext4fuse is on brew, but strangely unlisted for Mac, and listed for Linux, which it isn't for as far as I understand.

[albertskog]

Glad to hear you got it installed, I'll try too later!

I was mainly thinking of the second comment in that issue:

... From what I can gather, Homebrew has disabled a bunch of formula that use FUSE because it's no longer open source so they don't want it in the homebrew-core.

[pewulfman]

Did not try the workaround myself yet but see #66! It also gives some background, it's a licensing issue with macFuse..

Not sure where you got that it was a licensing issue. Anyhow, I did the manual .rb install and that seemingly worked. It still stands that ext4fuse is on brew, but strangely unlisted for Mac, and listed for Linux, which it isn't for as far as I understand.

That great ! @MisutaaAsriel, could you make a pull request to homebrew with your fix ? That would help a lot of people

[DavidInRacine]

Did not try the workaround myself yet but see #66! It also gives some background, it's a licensing issue with macFuse..

Not sure where you got that it was a licensing issue. Anyhow, I did the manual .rb install and that seemingly worked. It still stands that ext4fuse is on brew, but strangely unlisted for Mac, and listed for Linux, which it isn't for as far as I understand.

That great ! @MisutaaAsriel, could you make a pull request to homebrew with your fix ? That would help a lot of people

Seconding this request.

[bairain]

Same here in Monterey 12.7.3

[tezza1971]

Same here Ventura 13.5.1

[GwynethLlewelyn]

Ok, this is absurd :)

I would like to point out that there is ONE version of FUSE for macOS which does, indeed, have a tiny component which is free to copy and free to use but is not open-source.

But there are several FUSE packages for macOS these days. Namely, one that doesn't even run as a kernel extension (because Apple hates that), but rather as a clever hack on top of the NFSv4 filesystem component (which is very fast, and Apple loves that!). But there are more!

You can even still compile the ancient FUSE package that was open source, it will still work, at least for as long as Apple allows kernel extensions to run.

That said, it makes no sense to move ext4fuse— which runs on top of FUSE — outside the Homebrew repository.

---

Fortunately, ext4fuse compiles cleanly without a glitch! That way, there is no need to worry about Homebrew's weird policies...

[gustavopi]

I did have a look in this macos-fuse-t solution. However, it is made for developers to make their own apps including it, not for end users. I could not find any implementation of fuse-t anywhere, not even commend line one (there is examples only for Linux including to mount apfs :-/ ). There is still bloggers selling the idea that you can make use of ext4fuse, I doubt, and won't try it, thought Sonoma's kernel is very 'fragile'. That being said, the only way I know for years for ordinary users as myself to read/write ext4 filesystem is VirtualBox. Otherwise, whats left to us is to pay those 39 bucks to the pro guys of Paragon, every year.

[MisutaaAsriel]

Not sure where you got that it was a licensing issue. Anyhow, I did the manual .rb install and that seemingly worked. It still stands that ext4fuse is on brew, but strangely unlisted for Mac, and listed for Linux, which it isn't for as far as I understand.

That great ! @MisutaaAsriel, could you make a pull request to homebrew with your fix ? That would help a lot of people

Sorry for the late response but at the time I was not sure how I would go about a pull for this. Now, I don't really remember how I even did it (I'm sure I could find it again though). Usage was fickle, however, and being said, FSKit is on the horizon, with the potential for ext4fuse being superseded with a natively supported FSKit driver.

[GwynethLlewelyn]

Aww. FSKit is, unfortunately, designed for macOS 15.0+. Frankly, the way Apple wants to push users out from their ecosystem is simply terrible. Until then, well, we have to rely on whatever still works... ext4fuse works wonderfully well, it's just a pity we can only use it to read ext4 partitions...