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] [git commit] guile: use libltdl, needs dynamic libraries
Date: Mon, 30 Nov 2015 22:20:11 +0100	[thread overview]
Message-ID: <20151130222011.14df7412@free-electrons.com> (raw)
In-Reply-To: <87k2p5vxdn.fsf@dell.be.48ers.dk>

Peter,

On Thu, 26 Nov 2015 12:00:20 +0100, Peter Korsgaard wrote:

>  > from guile.mk. But it is weird, because I remember adding those three
>  > lines in guile.mk in commit 49593aba5a56c9c297c31c12fc4dc3de5679e7b1,
>  > and at the time, I tested a static build of guile and it worked fine.
>  > But maybe it was a static build with a dynamic capable toolchain, so I
>  > didn't see all the problems.
> 
> The problem is really about toolchains with dynamic library support but
> used in a static buildroot configuration. The libtool configure script
> detects that the system supports dlopen/dlsym and builds libltdl with
> that backend, but then later the guile configure script fails to link a
> test program with libltdl as it doesn't link with -ldl.
> 
> As far as I can see libltdl with a toolchain not supporting shared
> libraries doesn't do anything sensible. Perhaps libtool itself should
> depend on !BR2_STATIC_LIBS?

Perhaps, yes.

> With that said, I am not sure if guile works at runtime without shared
> libraries so I went with the safe approach of disallowing it for
> 2015.11.

Yes, and I also don't care about guile too much, and even less so in
static configurations :)

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

      reply	other threads:[~2015-11-30 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 22:10 [Buildroot] [git commit] guile: use libltdl, needs dynamic libraries Peter Korsgaard
2015-11-26  8:35 ` Thomas Petazzoni
2015-11-26 11:00   ` Peter Korsgaard
2015-11-30 21:20     ` 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=20151130222011.14df7412@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