All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: chromium detected as stripped
Date: Fri, 15 Sep 2017 14:05:28 +0200	[thread overview]
Message-ID: <87efr8p3p3.fsf@rkubodac-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CAHUNapTy3Lngxr0d2Gkd_2gFkZDcyYaumrEGTK6S8Aks5czhxw@mail.gmail.com> (Trevor Woerner's message of "Tue, 12 Sep 2017 21:31:09 -0700")

Trevor Woerner <twoerner@gmail.com> writes:

> On Wed, Aug 16, 2017 at 10:00 AM, Trevor Woerner <twoerner@gmail.com> wrote:
>> I won't submit anything to meta-browser until I can build and get it
>> running on a target (or multiple targets).
>
> I've been playing with this off-and-on for the past while. It looks
> really nice! Unfortunately I can't seem to get it to compile. Is there
> some secret I'm missing? I'm past all the openssl and gcc6/7 nonsense.
> All pre-requisites build fine, the build failure is (and has been for
> a while) with chromium itself.
>
> I've been trying to build it off master, but chromium always fails in
> breakpad. I won't bore you with the full build log (unless you really
> want to see it). My build setup is:
>
> Build Configuration:
> BB_VERSION        = "1.35.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "opensuse-42.2"
> TARGET_SYS        = "x86_64-oe-linux"
> MACHINE           = "qemux86-64"
> DISTRO            = "nodistro"
> DISTRO_VERSION    = "nodistro.0"
> TUNE_FEATURES     = "m64 core2"
> TARGET_FPU        = ""
> meta              = "master:2ebbeb61114e4b847e9164c621ac87b5cf03a299"
> meta-oe           = "master:8b991640f19f1d19b17db141c31bc56e26695a23"
> meta-crosswalk    = "chromium60:433371f15be4a16e1faab9e155d56edb572737d6"

Works For Me (TM), though I've only tested it with Yocto's pyro branch
so far. Also, do note that Chromium 61 is available in the chromium61
branch. Can you share the actual error you're getting in breakpad so I
could take a look?


  reply	other threads:[~2017-09-15 12:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12 23:10 chromium detected as stripped Andreas Müller
2017-08-14  7:04 ` Jussi Kukkonen
2017-08-14 10:22   ` Jussi Kukkonen
2017-08-14 14:10     ` Andreas Müller
2017-08-14 19:38       ` Andreas Müller
2017-08-14 19:43         ` Otavio Salvador
2017-08-14 21:51           ` Khem Raj
2017-08-15 13:05           ` Raphael Kubo da Costa
2017-08-15 14:18             ` Otavio Salvador
2017-08-15 14:43             ` Trevor Woerner
2017-08-15 14:47               ` Otavio Salvador
2017-08-15 16:14                 ` Khem Raj
2017-08-15 16:10               ` Khem Raj
2017-08-15 16:19             ` Khem Raj
2017-08-15 16:23               ` Raphael Kubo da Costa
2017-08-15 21:53                 ` Andreas Müller
2017-08-16 16:06                   ` Trevor Woerner
2017-08-16 16:12                     ` Martin Jansa
2017-08-16 16:17                       ` Khem Raj
2017-08-16 16:18                       ` Andreas Müller
2017-08-16 17:00                         ` Trevor Woerner
2017-09-13  4:31                           ` Trevor Woerner
2017-09-15 12:05                             ` Raphael Kubo da Costa [this message]
2017-09-19 14:33                     ` Raphael Kubo da Costa
2017-09-20 17:43                       ` Trevor Woerner
2017-09-21 23:06                         ` Trevor Woerner
2017-09-22 12:32                           ` Raphael Kubo da Costa
2017-09-23 20:53                             ` Trevor Woerner
2017-09-22 12:22                         ` Raphael Kubo da Costa

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=87efr8p3p3.fsf@rkubodac-desk.ger.corp.intel.com \
    --to=raphael.kubo.da.costa@intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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.