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] [autobuild.buildroot.net] Your build results for 2017-07-02
Date: Tue, 4 Jul 2017 11:23:49 +0200	[thread overview]
Message-ID: <20170704112349.3de1d628@windsurf> (raw)
In-Reply-To: <CAMRc=MfAxe99whmHQuBmBiWB7=mMjZEsZ6igT9XcsoQ9kXrkwg@mail.gmail.com>

Hello,

On Tue, 4 Jul 2017 11:10:02 +0200, Bartosz Golaszewski wrote:

> these failures are caused by missing the dynamic loader functionality
> in this pre-built toolchain. Should we maybe have a new config option
> like BR2_TOOLCHAIN_HAS_DL or something similar and depend on it from
> packages that need it?

Use "depends on !BR2_STATIC_LIBS", it's exactly meant for that.

Best regards,

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

      reply	other threads:[~2017-07-04  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170703063103.B69DB21E07@mail.free-electrons.com>
2017-07-03  7:05 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-07-02 Bartosz Golaszewski
2017-07-04  9:10 ` Bartosz Golaszewski
2017-07-04  9:23   ` 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=20170704112349.3de1d628@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