All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] enable static linking for libfuse
Date: Mon, 18 Dec 2017 07:25:57 +0100	[thread overview]
Message-ID: <20171218072557.169c472e@windsurf> (raw)
In-Reply-To: <CABukmmN5UjdWupf_8zuCkx13tuNVFxeD9AOE=cemfQ_Soe1AUQ@mail.gmail.com>

Hello,

On Sun, 17 Dec 2017 17:42:36 +0100, A EP wrote:
> yeah that's intentional. musl doesn't actually have separate libs. the
> empty libraries are just for compatibility.
> 
> i don't think dlopen actually works in static musl, it might just return 0.
> libfuse works fine for me, because it only uses dlopen for exotic modules
> stuff.

Then if you want to be able to have support for libfuse in static
builds in Buildroot, libfuse should only conditionally use dlopen(), if
available.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-12-18  6:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 10:57 [Buildroot] [PATCH 1/2] DTPMOD mod fix for musl's rcrt0 Arvid E. Picciani
2017-12-14 10:57 ` [Buildroot] [PATCH 2/2] enable static linking for libfuse Arvid E. Picciani
2017-12-14 15:21   ` Thomas Petazzoni
2017-12-14 15:27     ` Arvid Picciani
2017-12-14 15:52       ` Thomas Petazzoni
2017-12-15 13:12         ` Stefan Fröberg
2017-12-15 13:22           ` Stefan Fröberg
2017-12-15 14:10           ` Thomas Petazzoni
2017-12-15 13:07       ` Stefan Fröberg
     [not found]         ` <CABukmmN5UjdWupf_8zuCkx13tuNVFxeD9AOE=cemfQ_Soe1AUQ@mail.gmail.com>
2017-12-18  6:25           ` Thomas Petazzoni [this message]
2017-12-14 14:19 ` [Buildroot] [PATCH 1/2] DTPMOD mod fix for musl's rcrt0 Thomas Petazzoni

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=20171218072557.169c472e@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.