From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] gnutls: needs C++ support
Date: Tue, 27 Mar 2018 10:08:22 +0200 [thread overview]
Message-ID: <20180327100822.4ba3ac42@windsurf.home> (raw)
In-Reply-To: <87605it0kv.fsf@dell.be.48ers.dk>
Hello,
On Tue, 27 Mar 2018 09:54:56 +0200, Peter Korsgaard wrote:
> It is a bit stupid that we have pull in C++ support here and in all the
> reverse dependencies just because of a stupid configure check, but I
> guess it is the simplest/best solution.
>
> Should we then also revert bd39d11d2eaa679f (core/infra: fix build on
> toolchain without C++)?
>
> Yann, Thomas, Arnout - What do you say?
I just fired up a build to reproduce the issue and have a look. But
from what I remember last time I had a look, it was just some
completely brain-damaged autoconf sorcery, and there wasn't really any
hope of fixing it.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-27 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 20:23 [Buildroot] [PATCH v1 1/2] gnutls: needs C++ support Peter Seiderer
2018-03-21 20:23 ` [Buildroot] [PATCH v1 2/2] modem-manager: remove wrong gnutls dependency comment Peter Seiderer
2018-03-27 7:25 ` Petr Vorel
2018-03-27 7:50 ` Peter Korsgaard
2018-03-22 5:49 ` [Buildroot] [PATCH v1 1/2] gnutls: needs C++ support Baruch Siach
2018-03-22 12:10 ` Peter Seiderer
2018-03-22 13:51 ` Thomas Petazzoni
2018-03-27 7:54 ` Peter Korsgaard
2018-03-27 8:08 ` Thomas Petazzoni [this message]
2018-03-27 8:55 ` Yann E. MORIN
2018-03-27 7:56 ` Petr Vorel
2018-03-27 11:22 ` Peter Korsgaard
2018-03-27 14:23 ` Petr Vorel
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=20180327100822.4ba3ac42@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox