From: Martin Jansa <martin.jansa@gmail.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: Yocto Discussion Mailing List <yocto@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-freescale] Compile error for boost_1.54.0
Date: Tue, 9 Jul 2013 22:50:06 +0200 [thread overview]
Message-ID: <20130709205006.GW3288@jama> (raw)
In-Reply-To: <38DD74DA-F7B4-4D72-B00B-4B81076D784B@keylevel.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Tue, Jul 09, 2013 at 09:25:30PM +0100, Chris Tapp wrote:
> Forwarding to Yocto mailing list:
>
> On 9 Jul 2013, at 21:21, Otavio Salvador wrote:
>
> > On Tue, Jul 9, 2013 at 5:19 PM, Chris Tapp <opensource@keylevel.com> wrote:
> >>
> >> On 9 Jul 2013, at 20:09, Chris Tapp wrote:
> >>
> >>> I'm getting a failure in do_compile when building boost_1.54.0 using master-next for the wandboard-quad.
> >>>
> >>> The log is about 1.5MB, but the important bit seems to be that uintptr_t isn't defined but is required by /boost/atomic/atomic.hpp.
> >>>
> >>> Has anyone seen this before?
> >>
> >> I also meant to say that adding:
> >>
> >> typedef unsigned long long uintptr_t;
> >>
> >> to atomic.hpp 'fixes' the build, but this is not a good solution ;-)
> >
> > It needs to be checked against normal Poky to ensure it is BSP
> > specific; I doubt it is.
See
http://lists.openembedded.org/pipermail/openembedded-devel/2013-July/091331.html
But maybe it wasn't caused by eglibc upgrade (and header cleanup in
eglibc) but by boost upgrade.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-07-09 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 19:09 Compile error for boost_1.54.0 Chris Tapp
2013-07-09 20:19 ` Chris Tapp
2013-07-09 20:21 ` Otavio Salvador
2013-07-09 20:25 ` [meta-freescale] " Chris Tapp
2013-07-09 20:50 ` Martin Jansa [this message]
2013-07-10 3:17 ` Saul Wold
2013-07-10 4:19 ` Khem Raj
2013-07-10 5:04 ` Khem Raj
2013-07-11 19:27 ` Saul Wold
2013-07-11 19:38 ` Chris Tapp
2013-07-11 19:38 ` [yocto] " Chris Tapp
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=20130709205006.GW3288@jama \
--to=martin.jansa@gmail.com \
--cc=opensource@keylevel.com \
--cc=otavio@ossystems.com.br \
--cc=yocto@yoctoproject.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 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.