Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] cppunit: Added package
Date: Thu, 16 Oct 2014 12:11:43 +0200	[thread overview]
Message-ID: <543F99DF.1030103@mind.be> (raw)
In-Reply-To: <20141016115340.26569604@free-electrons.com>

On 16/10/14 11:53, Thomas Petazzoni wrote:
> 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.

 No, what I mean is: on platforms that do support shared libraries and packages
that support static-only, they will still detect that dlopen() is supported and
so they will still build support for dynamic libraries.

 But it's actually not a big deal, since they'll link with libdl.a so even at
runtime everything will work. I guess.


> 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.

 I don't know either.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-10-16 10:11 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
2014-10-16 10:11         ` Arnout Vandecappelle [this message]
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=543F99DF.1030103@mind.be \
    --to=arnout@mind.be \
    --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