All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Matt Weber <matthew.weber@rockwellcollins.com>
Cc: Chris Simons <chris.simons@rockwellcollins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] package/xml-security-c: new package
Date: Thu, 29 Jul 2021 00:05:18 +0200	[thread overview]
Message-ID: <20210729000518.64432265@windsurf> (raw)
In-Reply-To: <20210412162347.15021-1-matthew.weber@rockwellcollins.com>

Hello,

On Mon, 12 Apr 2021 11:23:47 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:

>  - Worked around Xerces_autoconf_config.hpp: error: ‘char16_t’ does not name a type
>    by disabling code sourcery toolchains
>    (ISO C++ forbids declaration - requires ISO C++ 2011 (code sourcery is GCC 4.8)

Meh, how come excluding a Code Sourcery toolchain is a solution to
this? My bug report on the v2 was not even related to a Code Sourcery
toolchain, so the work around proposed in this v3 doesn't even fix the
issue pointed out in v2.

Anyway, the problem is that this package was not passing -std=c++11
when building code, so the build fails on older compilers that did not
use C++11 as their default standard. So I have modified the package to
require gcc >= 4.7 and pass -std=c++11 in CXXFLAGS, and applied.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2021-07-28 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 16:23 [Buildroot] [PATCH v3] package/xml-security-c: new package Matt Weber
2021-07-28 22:05 ` Thomas Petazzoni [this message]

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=20210729000518.64432265@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=chris.simons@rockwellcollins.com \
    --cc=matthew.weber@rockwellcollins.com \
    /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.