All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] cppunit: Added package
Date: Thu, 16 Oct 2014 11:53:40 +0200	[thread overview]
Message-ID: <20141016115340.26569604@free-electrons.com> (raw)
In-Reply-To: <543F9315.3010104@mind.be>

Dear Arnout Vandecappelle,

On Thu, 16 Oct 2014 11:42:45 +0200, Arnout Vandecappelle wrote:

> > No: if it's really related to shared libraries, then it should be a
> > depends on !BR2_PREFER_STATIC_LIB.
> 
>  Yeah, you're probably right. It does build with PREFER_STATIC on other
> architectures, but that's just because there still is a dlopen in staging so it
> still sets CPPUNIT_HAVE_LIBDL and then it builds "correctly". But we most likely
> have many many packages that seem to build correctly with STATIC but actually
> still use shared libraries or dlopen. We probably should remove ld.so and
> libdl.* from staging when building static.

Well, for packages that do build on noMMU platforms, we do catch such
issues thanks to the bfin-uclinux toolchain configuration that is used
on the autobuilders. But for those other packages that don't build on
noMMU, we indeed don't check properly if we're able to do a pure static
build.

Alexey has sent a patch to remove HAVE_SHARED from the uClibc
configuration when BR2_PREFER_STATIC_LIB is enabled. Maybe this will
get rid of ld.so, libdl and so on? I haven't tested yet.

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

  reply	other threads:[~2014-10-16  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 20:22 [Buildroot] [PATCH v3] cppunit: Added package Sebastien Bourdelin
2014-10-16  8:15 ` Jerzy Grzegorek
2014-10-16  8:51 ` Arnout Vandecappelle
2014-10-16  9:08   ` Thomas Petazzoni
2014-10-16  9:42     ` Arnout Vandecappelle
2014-10-16  9:53       ` Thomas Petazzoni [this message]
2014-10-16 10:11         ` Arnout Vandecappelle
2014-10-16 15:37           ` Sebastien Bourdelin

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=20141016115340.26569604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.