From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Discussion of the angstrom distribution development
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: world build on angstrom-next
Date: Tue, 21 May 2013 23:04:23 +0200 [thread overview]
Message-ID: <20130521210423.GE32431@jama> (raw)
In-Reply-To: <CALbNGRTwzk+d+C2y_-PSKD4kWpkG_DEgDfCTGusSeCm6Wjz3qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]
On Tue, May 21, 2013 at 09:47:21PM +0200, Andreas Müller wrote:
> On Tue, May 21, 2013 at 9:32 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Tue, May 21, 2013 at 09:20:26PM +0200, Andreas Müller wrote:
> >> On Tue, May 21, 2013 at 8:16 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> > Hi All
> >> >
> >> > I have run world build on angstrom and here are results if anyone is interested and provide fixes.
> >> >
> >> > http://sakrah.dontexist.org/files/eglibc.beaglebone.world.log
> >> >
> >> > There are a lot of parsing errors especially from meta-opie
> >> >
> >> > Thanks
> >> > -Khem
> >> >
> >> Few errors should be fixed by my last series not yet applied (gtkhtml2
> >> / evince - this is not a ping :)
> >
> > I plan to push it today anyway, I was just waiting for khem's reply
> > about .inc merge :).
> >
> >> For chromium I have fixed some (not yet all) errors which came up with
> >> gcc 4.8 update. Looking into webkit-efl error messages I think there
> >> are similar issues (webkit). Hope to find the time to fix both next
> >> week.
> >
> > current webkit-efl revision was failing near the end while linking, but
> > I wanted to upgrade it anyways (I was using old revision mostly because
> > we didn't have harfbuzz when I was upgrading it for last time), but
> > it's hard to find newer working revision and what's even worse is that
> > only test app for webkit-efl (I know of) is eve which is quite abandoned
> > in upstream and every webkit-efl upgrade in the past required couple of
> > fixes in eve to support new APIs :/.
> >
> > Interestingly last revision I was building today r141868 fails in
> > different places for armv4t, armv5te+armv7a and qemux86-64 :).
> >
> I was also wondering of the passed chromium in the last logs you sent.
> Was this build performed with gcc 4.8 - or was there an update fixing
> builds with gcc 4.8 which I have missed?
My builds were with gcc-4.8 and I see chromium do_compile failing in my
last build and the same in khem's log
http://lists.linuxtogo.org/pipermail/openembedded-devel/2013-May/045634.html
| ../../third_party/webrtc/system_wrappers/interface/scoped_ptr.h: In
destructor 'webrtc::scoped_ptr<T>::~scoped_ptr()':
| ../../third_party/webrtc/system_wrappers/interface/scoped_ptr.h:55:18:
error: typedef 'type_must_be_complete' locally defined but not used
[-Werror=unused-local-typedefs]
| typedef char type_must_be_complete[sizeof(T)];
| ^
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-05-21 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 18:16 world build on angstrom-next Khem Raj
2013-05-21 19:20 ` Andreas Müller
2013-05-21 19:32 ` Martin Jansa
2013-05-21 19:47 ` Andreas Müller
2013-05-21 19:50 ` Khem Raj
2013-05-21 21:04 ` Martin Jansa [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=20130521210423.GE32431@jama \
--to=martin.jansa@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.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 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.