mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: genieplus <genieplus@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Can not build Casablanca-2.3.0 with arm-v5te-linux-gnueabi-gcc-4.8.2-glibc-2.18-binutils-2.24-kernel-3.12-sanitized
Date: Fri, 9 Jan 2015 15:55:54 +0100	[thread overview]
Message-ID: <CAJ2U5c4ZEk53BVGfnOYuaP2oLKSuwzpKUZMRF6FnzOcZ-B0yaw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]

Hi,

I am currently trying to build Casablanca [https://casablanca.codeplex.com/]
for my ARM board using the toolchain
gcc-4.8.2-glibc-2.18-binutils-2.24-kernel-3.12-sanitized
(from OSELAS.Toolchain-2013.12.2) and ptxdist-2014.12.0.

The compilation fails with a lot of errors related to the C++11 standard.
For example:

build-target/casablanca-2.3.0/tests/common/UnitTestpp/src/TestRunner.cpp:41:0:
/opt/OSELAS.Toolchain-2013.12.2/arm-v5te-linux-gnueabi/gcc-4.8.2-glibc-2.18-binutils-2.24-kernel-3.12-sanitized/arm-v5te-linux-gnueabi/include/c++/4.8.2/future:113:11:
error: declaration of 'class std::future<void>'
     class future;


I am able to build the same version of Casablanca on my x86 machine using
gcc version 4.8.2 (Ubuntu 4.8.2.-19ubuntu1).

Am I doing something wrong, or this version of
arm-v5te-linux-gnueabi-gcc-4.8.2 do not have the same support of C++11
features as the desktop version?

Regards,
Bechir

[-- Attachment #1.2: Type: text/html, Size: 3166 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-01-09 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 14:55 genieplus [this message]
2015-01-14 10:35 ` Michael Olbrich

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=CAJ2U5c4ZEk53BVGfnOYuaP2oLKSuwzpKUZMRF6FnzOcZ-B0yaw@mail.gmail.com \
    --to=genieplus@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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