From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [v2 1/1] make: disable guile support when static linking enabled
Date: Mon, 12 Oct 2015 23:57:36 +0200 [thread overview]
Message-ID: <20151012235736.117283b6@free-electrons.com> (raw)
In-Reply-To: <1442783430-26199-1-git-send-email-ryanbarnett3@gmail.com>
Dear Ryan Barnett,
On Sun, 20 Sep 2015 16:10:30 -0500, Ryan Barnett wrote:
> When building in a static only configuration with guile package
> enabled, the following error happens:
>
> gc_pthread_redirects.h:37:22: fatal error: dlfcn.h: No such file or
> directory
> # include <dlfcn.h>
>
> The file gc_pthread_redirects.h comes from bdwgc, which gets built
> before make in the autobuild test case you're pointing to. This header
> file is known to incorrectly include <dlfcn.h>, unless GC_NO_DLOPEN is
> specified.
>
> IF GC_NO_DLOPEN is defined, another issue arises due to libguile and
> libintl both defining locale_charset.
>
> Thus disable guile support for make.
>
> Fixes:
> http://autobuild.buildroot.net/results/814/8143ae0afac139845e5016058d85c800dc8527ad
>
> Signed-off-by: Ryan Barnett <ryanbarnett3@gmail.com>
> ---
> package/make/make.mk | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
Applied after tweaking the commit log, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-12 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 21:10 [Buildroot] [v2 1/1] make: disable guile support when static linking enabled Ryan Barnett
2015-09-20 21:51 ` Yann E. MORIN
2015-09-20 22:00 ` Ryan Barnett
2015-09-21 17:25 ` Yann E. MORIN
2015-10-12 21:57 ` Thomas Petazzoni [this message]
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=20151012235736.117283b6@free-electrons.com \
--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