Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure failure with libfuse 3.x #3

Open
rbberger opened this issue Nov 21, 2024 · 8 comments
Open

Configure failure with libfuse 3.x #3

rbberger opened this issue Nov 21, 2024 · 8 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@rbberger
Copy link

The configure script fails with libfuse newer than 2.x

@hppritcha
Copy link

this is an issue on our grace hopper system.

@jswaro
Copy link
Contributor

jswaro commented Jan 13, 2025

Please share the result of how it fails with libfuse 3. Libcxi does not currently support libfuse 3 and the team is not actively investigating those changes at this time.

If the delta is small or if someone proposes a PR here, then it could be considered for merge.

@boeschf
Copy link

boeschf commented Jan 15, 2025

FYI, libfuse 2.xx does not compile on arm64 (grace hopper). Howver, this patch for libfuse 2.9.9 resolves the compilation error (found at https://patchwork.ozlabs.org/project/openwrt/patch/[email protected]/)

diff --git i/include/fuse_kernel.h w/include/fuse_kernel.h
index c632b58..9e02fe3 100644
--- i/include/fuse_kernel.h
+++ w/include/fuse_kernel.h
@@ -88,12 +88,16 @@
 #ifndef _LINUX_FUSE_H
 #define _LINUX_FUSE_H
 
-#include <sys/types.h>
+#ifdef __linux__
+#include <linux/types.h>
+#else
+#include <stdint.h>
 #define __u64 uint64_t
 #define __s64 int64_t
 #define __u32 uint32_t
 #define __s32 int32_t
 #define __u16 uint16_t
+#endif
 
 /*
  * Version negotiation:

@hppritcha
Copy link

thanks that should do @boeschf .

@rbberger
Copy link
Author

@hppritcha in Spack I've submitted this: spack/spack#47846

@jswaro
Copy link
Contributor

jswaro commented Jan 16, 2025

Then this can be closed ? @rbberger / @hppritcha

@rbberger
Copy link
Author

I would hope this would get closed once libfuse 3.x is supported. What we have are workarounds forcing the use the older version when possible.

@jswaro jswaro added enhancement New feature or request good first issue Good for newcomers labels Jan 23, 2025
@jswaro
Copy link
Contributor

jswaro commented Jan 23, 2025

Sounds fine. I'll leave it open, but I do not have an expected date for completion. This is low priority for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants