From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/squid: depends on current_exception
Date: Thu, 6 Sep 2018 23:27:49 +0200 [thread overview]
Message-ID: <20180906232749.6fbfd857@windsurf.home> (raw)
In-Reply-To: <20180824200107.22849-1-bernd.kuhls@t-online.de>
Hello,
On Fri, 24 Aug 2018 22:01:07 +0200, Bernd Kuhls wrote:
> Fixes build error
>
> TextException.cc: In function 'std::ostream& CurrentException(std::ostream&)':
> TextException.cc:64:9: error: 'current_exception' is not a member of 'std'
> if (std::current_exception()) {
>
> using this defconfig
>
> BR2_arm=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
> BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
> BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/armv5-ctng-linux-gnueabi.tar.xz"
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="armv5-ctng-linux-gnueabi"
> BR2_TOOLCHAIN_EXTERNAL_GCC_4_8=y
> BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_12=y
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
> BR2_TOOLCHAIN_EXTERNAL_CXX=y
> BR2_PACKAGE_GNUTLS=y
> BR2_PACKAGE_OPENSSL=y
> BR2_PACKAGE_LIBKRB5=y
>
> According to http://www.squid-cache.org/Versions/v4/RELEASENOTES.html#ss1.1
> squid-4.2 depends on C++11, but adding -std=c++11 did not fix the build
> error.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
I have indeed verified that std::current_exception() is made available
to all platforms when the bug 64375 is fixed in gcc.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-06 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 20:01 [Buildroot] [PATCH/next 1/1] package/squid: depends on current_exception Bernd Kuhls
2018-09-03 13:50 ` Giulio Benetti
2018-09-06 21:27 ` Thomas Petazzoni [this message]
2018-09-08 21:39 ` Thomas Petazzoni
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=20180906232749.6fbfd857@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