[maxlepikhin]

Summary

• Repair the OSS EdenFS build graph and Rust/C++ bridge generation so the daemon and privileged helper build on macOS arm64 with getdeps-managed dependencies.
• Build and package the modern Python edenfsctl with its Folly and Thrift runtime when EDEN_USE_THRIFT_PYTHON_CLI=ON. The targeted build uses EDEN_BUILD_INTEGRATION_TESTS=OFF.
• Avoid selecting pipe2 in Eden common on macOS, where a binary built with the macOS 27 SDK can crash at startup on macOS 26.

Addresses #1478.

Test Plan

• Built edenfs and edenfs_privhelper from the current main dependency revisions on macOS arm64. The resulting daemon starts far enough for edenfs --version and reports edenfs.
• Verified the macOS-only BLAKE3 configuration removes the duplicate C symbol from the aggregate Rust archive.
• Validated all changed getdeps manifests and verified the Eden common and fbthrift patches apply to their pinned revisions.
• An earlier build of this branch started the daemon and privileged helper, mounted an EdenFS NFS checkout, and completed a Bazel //:hello build in that checkout.
• Linux EdenFS was not built locally. A macOS EdenFS CI build would add regression coverage.

[meta-codesync]

This pull request has been imported. If you are a Meta employee, you can view this in D127498188. (Because this pull request was imported automatically, there will not be any future comments.)

[genevievehelsel]

Hi @maxlepikhin - thanks for the PR. I have a stack that I'm working on that should get EdenFS buildable and runnable with cmake. It's about halfway done, I'll try to get that landed ASAP and then will take a look at this PR. Even after I land my stack, I think your PR will still have changes to merge and land that my stack doesn't cover. For example, I built on macOS 26 and I see you have a macOS 27 fix.

[maxlepikhin]

Hi @maxlepikhin - thanks for the PR. I have a stack that I'm working on that should get EdenFS buildable and runnable with cmake. It's about halfway done, I'll try to get that landed ASAP and then will take a look at this PR. Even after I land my stack, I think your PR will still have changes to merge and land that my stack doesn't cover. For example, I built on macOS 26 and I see you have a macOS 27 fix.

The changes in this PR make it buildable and runnable on MacOS 26, it worked for me.

[facebook-github-tools]

@maxlepikhin has updated the pull request. You must reimport the pull request before landing.

[facebook-github-tools]

@maxlepikhin has updated the pull request. You must reimport the pull request before landing.

[facebook-github-tools]

@maxlepikhin has updated the pull request. You must reimport the pull request before landing.