Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15221] New: FUSE filesystems can be statically compiled
Date: Mon, 02 Jan 2023 13:32:00 +0000	[thread overview]
Message-ID: <bug-15221-163@https.bugs.busybox.net/> (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: unassigned@buildroot.uclibc.org
          Reporter: tomas@slax.org
                CC: buildroot@uclibc.org
  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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-01-02 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 13:32 bugzilla [this message]
2024-06-15 15:04 ` [Buildroot] [Bug 15221] FUSE filesystems can be statically compiled bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15221-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox