From: Ian Coolidge <ian@boundarydevices.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] CFT: Chromium 62 in meta-browser
Date: Mon, 13 Nov 2017 13:51:17 -0800 [thread overview]
Message-ID: <CADseiPnGDYTz-Ht=kTxGt+UpfeNx-Q6dGY-jOa=11JgvOEcuGQ@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKqhY9miP9wf0rv_mhtyn9_dV6-Cm3=J6yOhmx-Y6qpGiw@mail.gmail.com>
Where is this commit? I don't see 568227133be3f9f015679df3525f6c4f86304fd0
in meta-browser?
On Sat, Nov 11, 2017 at 9:25 AM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:
> On Fri, Nov 10, 2017 at 10:10 PM, Ian Coolidge <ian@boundarydevices.com>
> wrote:
> ...
> > Are there any obvious flags or compile options I'm missing here? I
> haven't
> > tied debugging into this yet, which is my next step here. Just wanted to
> > know if I was missing something obvious.
>
> Maybe this fixes it?
>
> commit 568227133be3f9f015679df3525f6c4f86304fd0
> Author: Khem Raj <raj.khem@gmail.com>
> Date: Tue Nov 7 15:26:52 2017 -0800
>
> gcc7/gcc6: Fix unaligned STRD issue on ARM
>
> Backport
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82445
>
> Fixes [YOCTO 12297]
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
>
> Please check if it helps you, otherwise please open a github issue so
> we can keep track of it.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>
next prev parent reply other threads:[~2017-11-13 21:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 16:28 [meta-browser] CFT: Chromium 62 in meta-browser Raphael Kubo da Costa
2017-11-09 16:54 ` Otavio Salvador
2017-11-09 17:08 ` Raphael Kubo da Costa
2017-11-10 19:49 ` Trevor Woerner
2017-11-11 0:10 ` Ian Coolidge
2017-11-11 17:25 ` Otavio Salvador
2017-11-13 21:51 ` Ian Coolidge [this message]
2017-11-13 21:56 ` Ian Coolidge
2017-11-15 12:04 ` Raphael Kubo da Costa
2017-11-15 12:38 ` Martin Jansa
2017-11-15 14:20 ` Martin Jansa
2017-11-15 17:08 ` Raphael Kubo da Costa
2017-11-15 17:41 ` Martin Jansa
2017-11-15 17:49 ` Kubo Da Costa, Raphael
2017-11-15 19:34 ` Khem Raj
2017-11-23 10:22 ` Ayoub Zaki
2017-11-28 0:52 ` Ian Coolidge
2017-11-28 8:13 ` Ayoub Zaki
2017-11-28 11:58 ` Otavio Salvador
2017-11-28 12:47 ` Ayoub Zaki
2017-11-28 13:05 ` Otavio Salvador
2017-11-28 21:44 ` Ian Coolidge
2017-12-11 11:30 ` Raphael Kubo da Costa
2017-12-11 11:35 ` Ayoub Zaki
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='CADseiPnGDYTz-Ht=kTxGt+UpfeNx-Q6dGY-jOa=11JgvOEcuGQ@mail.gmail.com' \
--to=ian@boundarydevices.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.