Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bug during Kodi compile with host gcc <4.7, question regarding autobuilders
Date: Mon, 14 Mar 2016 23:05:03 +0100	[thread overview]
Message-ID: <20160314230503.0eab7efe@free-electrons.com> (raw)
In-Reply-To: <4mfjrcxqge.ln2@ID-313208.user.individual.net>

Hello,

On Mon, 14 Mar 2016 20:23:16 +0100, Bernd Kuhls wrote:

> with my proposed patch we can lower it to BR2_HOST_GCC_AT_LEAST_4_6 ;)
> 
> With gcc 4.4 (testing with Ubuntu 10.04.4) adding -std=c++0xwill not be 
> enough:
> 
> XBTFWriter.cpp: In constructor ?CXBTFWriter::CXBTFWriter(const 
> std::string&)?:
> XBTFWriter.cpp:42: error: ?nullptr? was not declared in this scope
> 
> Looking around for approaches to solve the problem I found these two 
> commits:
> 
> https://hg.mozilla.org/integration/mozilla-inbound/rev/ae45a2c9d678
> https://github.com/grpc/grpc/
> commit/3ff350cf96676f2c32c6913aceeabf84a15f3715

Why do you want to solve the problem? Adding a dependency on
BR2_HOST_GCC_AT_LEAST_4_6 is perfectly fine, especially for such
a modern, complex C++ software like Kodi.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-03-14 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13 21:53 [Buildroot] Bug during Kodi compile with host gcc <4.7, question regarding autobuilders Bernd Kuhls
2016-03-13 22:19 ` Arnout Vandecappelle
2016-03-14 13:31   ` Peter Korsgaard
2016-03-14 13:42     ` Thomas Petazzoni
2016-03-14 19:23   ` Bernd Kuhls
2016-03-14 22:05     ` Thomas Petazzoni [this message]
2016-03-15 22:08       ` Yann E. MORIN
2016-03-17 20:54       ` Bernd Kuhls

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=20160314230503.0eab7efe@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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