Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] About static linking
Date: Fri, 25 Apr 2014 00:01:49 +0200	[thread overview]
Message-ID: <535989CD.9090105@mind.be> (raw)
In-Reply-To: <87tx9i21li.fsf@dell.be.48ers.dk>

On 24/04/14 17:23, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  > Dear Baruch Siach,
>  > On Wed, 23 Apr 2014 22:59:59 +0300, Baruch Siach wrote:
> 
>  >> +DHCPDUMP_LIBS = -lpcap
>  >> +ifeq ($(BR2_PREFER_STATIC_LIB),y)
>  >> +DHCPDUMP_LIBS += $(shell $(STAGING_DIR)/usr/bin/pcap-config --static --additional-libs)
>  >> +endif
> 
>  > This is not at all against your patch specifically, but I'm a bit
>  > worried about all the static linking related kludges we add all over
>  > the place. Is this normal? Shouldn't we fix the packages themselves and
>  > submit patches upstream?
> 
> It would certainly be nice to get these things handled upstream, but
> it's similar to the special-archs/nommu/uClibc stuff, E.G. not something
> "normal" people gets affected by (and something we have decided to
> support), so I don't think there's much else we can do.

 Still, I expect that upstreams are more likely to be willing to accept
patches for linking against a static library than patches for exotic
systems. Especially since the former is usually only a config patch,
while the special-archs/nommu/uClibc stuff is more likely to affect the
code itself.

 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-04-24 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 19:59 [Buildroot] [PATCH] dhcpdump: fix static build Baruch Siach
2014-04-23 20:52 ` [Buildroot] About static linking Thomas Petazzoni
2014-04-24  4:29   ` Baruch Siach
2014-04-24  7:16     ` Thomas Petazzoni
2014-04-24 15:23   ` Peter Korsgaard
2014-04-24 22:01     ` Arnout Vandecappelle [this message]
2014-05-07 20:48 ` [Buildroot] [PATCH] dhcpdump: fix static build 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=535989CD.9090105@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