From: Trevor Woerner <twoerner@gmail.com>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: binutils upgrade to 2.26 failure - unsupported reloc 42 against global symbol __gmon_start__
Date: Wed, 3 Feb 2016 14:29:04 -0500 [thread overview]
Message-ID: <56B25500.7030402@gmail.com> (raw)
My chromium build is now failing due to:
commit 86ade2cc2553c942d9526c5323a11ae151653505
binutils: Upgrade to 2.26
| FAILED: x86_64-oe-linux-gcc -m64 -march=corei7 -mtune=corei7
-mfpmath=sse -msse4.2
--sysroot=/z/chromium-49/build/tmp-glibc/sysroots/intel-corei7-64
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,now -Wl,-z,relro
-Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC
-B/z/chromium-49/build/tmp-glibc/work/corei7-64-oe-linux/chromium/49.0.2612.0-r0/chromium-49.0.2612.0/third_party/binutils/Linux_x64/Release/bin
-Wl,--disable-new-dtags -m64 -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections
-o chrome_sandbox -Wl,--start-group
obj/sandbox/linux/suid/chrome_sandbox.process_util_linux.o
obj/sandbox/linux/suid/chrome_sandbox.sandbox.o -Wl,--end-group
|
/z/chromium-49/build/tmp-glibc/work/corei7-64-oe-linux/chromium/49.0.2612.0-r0/chromium-49.0.2612.0/third_party/binutils/Linux_x64/Release/bin/ld:
error:
/z/chromium-49/build/tmp-glibc/sysroots/intel-corei7-64/usr/lib/../lib/crti.o:
unsupported reloc 42 against global symbol __gmon_start__
| ../sysdeps/x86_64/crti.S:66: error: unsupported reloc 42
Any suggestions on how to approach this?
next reply other threads:[~2016-02-03 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 19:29 Trevor Woerner [this message]
2016-02-03 19:56 ` binutils upgrade to 2.26 failure - unsupported reloc 42 against global symbol __gmon_start__ 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
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=56B25500.7030402@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