From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] gnutls: needs C++ support
Date: Thu, 22 Mar 2018 14:51:50 +0100 [thread overview]
Message-ID: <20180322145150.2f72d018@windsurf> (raw)
In-Reply-To: <20180322054912.akgs3lgdfgiiee6s@sapphire.tkos.co.il>
Hello,
On Thu, 22 Mar 2018 07:49:13 +0200, Baruch Siach wrote:
> On Wed, Mar 21, 2018 at 09:23:11PM +0100, Peter Seiderer wrote:
> > Fixes Bug 10846 ([1]):
> >
> > checking how to run the C++ preprocessor... cpp
> > configure: error: in `.../build/gnutls-3.5.17':
> > configure: error: C++ preprocessor "cpp" fails sanity check
> > See `config.log' for more details
> >
> > [1] https://bugs.busybox.net/show_bug.cgi?id=10846
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> This is strange. Do you have idea why the autobuilders didn't catch that?
We don't have any toolchain configuration in the autobuilders that has
wchar support enabled, but C++ support disabled.
We do have a configuration that is basic (no wchar, no C++), but since
gnutls already depends on wchar, it was never tested with this
toolchain.
Hence, this doesn't pop-up in the autobuilders.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-22 13:51 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 [this message]
2018-03-27 7:54 ` Peter Korsgaard
2018-03-27 8:08 ` Thomas Petazzoni
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=20180322145150.2f72d018@windsurf \
--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.