From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/1] package/wireshark: fix static build with snappy
Date: Tue, 28 May 2019 22:42:35 +0200 [thread overview]
Message-ID: <20190528224235.7b5a2647@windsurf.home> (raw)
In-Reply-To: <20190528203230.24558-1-fontaine.fabrice@gmail.com>
Hello,
On Tue, 28 May 2019 22:32:30 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/419468f0d7d3c2b64d420513aa9505c6de097ed2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2 (after review of Arnout Vandecappelle):
> - Set linker to CXX instead of adding -lstdc++ to LIBS
Is this really the right thing to do? Ideally a program written in C
should not have to know that a library it is using is written in C++.
We already had a similar situation in Buildroot, and so far we have
added -lstdc++. For example:
ifeq ($(BR2_PACKAGE_DIRECTFB),y)
LINKS_CONF_ENV = ac_cv_path_DIRECTFB_CONFIG=$(STAGING_DIR)/usr/bin/directfb-config
ifeq ($(BR2_STATIC_LIBS),y)
LINKS_CONF_ENV += LIBS=-lstdc++
and there's a few other examples in the tree. To be honest, I don't
know what is the most correct solution, I'm just trying to make sure we
solve a given problem in the same way everywhere.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-28 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:32 [Buildroot] [PATCH v2, 1/1] package/wireshark: fix static build with snappy Fabrice Fontaine
2019-05-28 20:42 ` Thomas Petazzoni [this message]
2019-05-28 20:48 ` Fabrice Fontaine
2019-05-28 21:04 ` Arnout Vandecappelle
2019-05-29 6:53 ` Thomas Petazzoni
2019-05-29 8:49 ` Arnout Vandecappelle
2019-05-29 9:15 ` Fabrice Fontaine
2020-01-10 17:37 ` Yann E. MORIN
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=20190528224235.7b5a2647@windsurf.home \
--to=thomas.petazzoni@bootlin.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.