Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: binutils upgrade to 2.26 failure - unsupported reloc 42 against global symbol __gmon_start__
Date: Wed, 3 Feb 2016 22:06:20 -0500	[thread overview]
Message-ID: <56B2C02C.90607@gmail.com> (raw)
In-Reply-To: <CA+chaQd2Cdzpo0_LP2mJUoYe8UtwmOK3DCpE-yXk_s80t41QSA@mail.gmail.com>

On 02/03/16 15:32, Martin Jansa wrote:
> This could be caused by chromium using own bundled binutils where the 
> version doesn't match, I've solved it in our recipe by:
> +GYP_DEFINES_append = " linux_use_bundled_gold=0"
> +GYP_DEFINES_append = " linux_use_bundled_binutils=0"

w00t!! awesome. works for me :-)

So it looks like we both have working chromium recipes, yet the upstream 
one doesn't work. What version are you building? For what arch (which 
archs)? x11/wayland?

I have a working recipe for 50.0.2636.0, but I'm only interested in 
x86_64 and x11. wayland+ozone is a whole other mess ;-)

At some point it'll probably be easier if we build chromium with 
llvm-clang, the same as google is doing. Is that possible?


  parent reply	other threads:[~2016-02-04  3:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 19:29 binutils upgrade to 2.26 failure - unsupported reloc 42 against global symbol __gmon_start__ Trevor Woerner
2016-02-03 19:56 ` Khem Raj
2016-02-03 20:09   ` Paul Eggleton
2016-02-03 20:21     ` Khem Raj
2016-02-03 20:32       ` Martin Jansa
2016-02-03 20:50         ` Khem Raj
2016-02-03 20:55         ` Burton, Ross
2016-02-04  3:06         ` Trevor Woerner [this message]
2016-02-04  3:08           ` Khem Raj
2016-02-04  3:30             ` Trevor Woerner
2016-02-04  3:46               ` Dan McGregor
2016-02-04  4:24               ` Khem Raj
2016-02-03 20:27   ` Trevor Woerner

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=56B2C02C.90607@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@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