From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Khem Raj : eglibc: Add 2.18 recipes
Date: Mon, 8 Jul 2013 14:10:48 +0200 [thread overview]
Message-ID: <20130708121048.GK3288@jama> (raw)
In-Reply-To: <20130705143917.C20B35040C@opal>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Fri, Jul 05, 2013 at 02:39:17PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 59ae9fc07a6a89492c001de0b3322ecd6d3956be
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=59ae9fc07a6a89492c001de0b3322ecd6d3956be
>
> Author: Khem Raj <raj.khem@gmail.com>
> Date: Wed Jun 26 13:59:01 2013 -0700
>
> eglibc: Add 2.18 recipes
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
boost is now failing on all architectures
./boost/atomic/atomic.hpp: At global scope:
./boost/atomic/atomic.hpp:202:16: error: 'uintptr_t' was not declared in this scope
typedef atomic<uintptr_t> atomic_uintptr_t;
^
./boost/atomic/atomic.hpp:202:25: error: template argument 1 is invalid
typedef atomic<uintptr_t> atomic_uintptr_t;
^
./boost/atomic/atomic.hpp:202:43: error: invalid type in declaration before ';' token
typedef atomic<uintptr_t> atomic_uintptr_t;
^
Adding
#include <stdint.h> in boost/atomic/atomic.hpp solves that, but
#include <cstdint> doesn't, is it right fix?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next parent reply other threads:[~2013-07-08 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130705143917.C20B35040C@opal>
2013-07-08 12:10 ` Martin Jansa [this message]
2013-07-09 9:43 ` [oe-commits] Khem Raj : eglibc: Add 2.18 recipes Jonathan Liu
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=20130708121048.GK3288@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/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