Skip to contentSkip to conversation

New: FUSE filesystems can be statically compiled

Buildroot [email protected] 1 participant 2 messages Jan 2, 2023 – Jun 15, 2024

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=15221

Bug ID: 15221
Summary: FUSE filesystems can be statically compiled
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---

I can see the FUSE library as well as the fuse-based filesystems are marked to require dynamic library linking, because it does not compile with uclibc statically.

However, if I select to use musl instead of uclibc, and if I make the necessary changes to let libfuse and other fuse filesystems to compile statically, then it works just fine. It compiles statically with musl and works OK.

I have no idea if it is possible to mark a package requiring dynamic linking ONLY IF uclibc is selected, but if this possibility exists, you should consider it, because if user selects musl, there is no need for him to disable static linking.

Thanks for consideration
Tomas M

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#1 lore raw

[Buildroot] [Bug 15221] FUSE filesystems can be statically compiled

https://bugs.busybox.net/show_bug.cgi?id=15221

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |MOVED
                 CC|                            |[email protected]
             Status|NEW                         |RESOLVED

--- Comment #1 from Yann E. MORIN <[email protected]> --- Thank you for your report.

The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker.

Thank you!

Signature · 6 lines
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot