Buildroot Archive on 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: Thu, 14 Dec 2017 16:21:02 +0100	[thread overview]
Message-ID: <20171214162102.25c6d252@windsurf> (raw)
In-Reply-To: <20171214105706.4577-2-aep@exys.org>

Hello,

Thanks for your contribution. However...

On Thu, 14 Dec 2017 11:57:06 +0100, Arvid E. Picciani wrote:
> Signed-off-by: Arvid E. Picciani <aep@exys.org>
> ---
>  package/libfuse/Config.in  | 4 ----
>  package/libfuse/libfuse.mk | 3 ++-
>  2 files changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/package/libfuse/Config.in b/package/libfuse/Config.in
> index 2b0e31a991..62b18c2444 100644
> --- a/package/libfuse/Config.in
> +++ b/package/libfuse/Config.in
> @@ -1,7 +1,6 @@
>  config BR2_PACKAGE_LIBFUSE
>  	bool "libfuse"
>  	# Really doesn't like static, see fuse/lib/fuse.c

...did you see this comment?

fuse.c uses dlopen(), this requires shared library support.

Apply your patch, and build the following configuration:

BR2_arm=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-static-2017.11-rc1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_6=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_10=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_LIBFUSE=y
# BR2_TARGET_ROOTFS_TAR is not set

You'll get the following build failure:

fuse.c:33:19: fatal error: dlfcn.h: No such file or directory
 #include <dlfcn.h>
                   ^
compilation terminated.

Also, passing --enable-static is not necessary, this is already done by
the autotools-package infrastructure when BR2_STATIC_LIBS=y.

Best regards,

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

  reply	other threads:[~2017-12-14 15:21 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 [this message]
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
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=20171214162102.25c6d252@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox