Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/sconeserver: needs shared libs or non uClibc toolchain
Date: Mon, 29 Aug 2016 09:03:53 +0200	[thread overview]
Message-ID: <87k2f06opy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160828221524.GF5758@free.fr> (Yann E. MORIN's message of "Mon,  29 Aug 2016 00:15:24 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 >> Ehh, this I don't get. Why not simply depend on !BR2_STATIC_LIBS like we
 >> do for other users of dlfcn.h?
 >> 
 >> If BR2_STATIC_LIBS is enabled then there won't be any .so files in the
 >> target rootfs, so even if the C library has dlopen support it won't
 >> work.

 > Not necessarily true.

 > One can use dlopen() to load "addons" even from a staticaly linked
 > executable.

Generally speaking, yes - But not in Buildroot. We have a single global
BR2_STATIC_LIBS setting, so it is all or nothing.

 > However, I don't care about sconeserver; I was just looking at build
 > failures and trying to make it the least broken as possible.

 > If you're fine with making it depend on non static-only and drop the
 > uclibc condition, that's fine with me. ;-)

Ok, I'll adjust the patch and commit message and apply, thanks.

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2016-08-29  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 18:19 [Buildroot] [PATCH 1/2] package/sconeserver: needs host-pkgconf Yann E. MORIN
2016-08-28 18:19 ` [Buildroot] [PATCH 2/2] package/sconeserver: needs shared libs or non uClibc toolchain Yann E. MORIN
2016-08-28 22:09   ` Peter Korsgaard
2016-08-28 22:15     ` Yann E. MORIN
2016-08-29  7:03       ` Peter Korsgaard [this message]
2016-08-28 22:20   ` Matthew Weber
2016-08-28 22:05 ` [Buildroot] [PATCH 1/2] package/sconeserver: needs host-pkgconf Peter Korsgaard

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=87k2f06opy.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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