From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-browser] Chromium and gold linker
Date: Mon, 10 Jul 2017 16:36:42 -0400 [thread overview]
Message-ID: <20170710203642.GB26405@denix.org> (raw)
Khem, et al,
I couldn't find below patch being discussed on this mailing list before it got
merged:
https://github.com/OSSystems/meta-browser/commit/62e323848f569c4cdea5567b1917ce006d7705af
According to the layer README, openembedded-devel is the official mailing list
to submit patches. I understand that github pull request is a nice shortcut,
but it prevents others from seeing and commenting on the patches...
My issue with this change is that it makes an assumption of using OE-built
toolchain. It now breaks external toolchains like this:
| [17/20569] LINK genmacro
| FAILED: genmacro
| gcc -L/opt/linaro-2016.11/arm-linux-gnueabihf/lib -Wl,-rpath-link,/opt/linaro-2016.11/arm-linux-gnueabihf/lib -Wl,-O1 -Wl,--hash-style=gnu -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -Wl,--no-as-needed -lpthread -Wl,--as-needed -o genmacro -Wl,--start-group obj.host/third_party/yasm/source/patched-yasm/tools/genmacro/genmacro.genmacro.o -Wl,--end-group
| /usr/bin/ld.gold: fatal error: /opt/linaro-2016.11/arm-linux-gnueabihf/lib/libgcc_s.so.1: unsupported ELF machine number 40
| collect2: error: ld returned 1 exit status
| [18/20569] LINK genstring
| FAILED: genstring
| gcc -L/opt/linaro-2016.11/arm-linux-gnueabihf/lib -Wl,-rpath-link,/opt/linaro-2016.11/arm-linux-gnueabihf/lib -Wl,-O1 -Wl,--hash-style=gnu -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -Wl,--no-as-needed -lpthread -Wl,--as-needed -o genstring -Wl,--start-group obj.host/third_party/yasm/source/patched-yasm/genstring.genstring.o -Wl,--end-group
| /usr/bin/ld.gold: fatal error: /opt/linaro-2016.11/arm-linux-gnueabihf/lib/libgcc_s.so.1: unsupported ELF machine number 40
| collect2: error: ld returned 1 exit status
--
Denys
next reply other threads:[~2017-07-10 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:36 Denys Dmytriyenko [this message]
2017-07-10 20:47 ` [meta-browser] Chromium and gold linker Denys Dmytriyenko
2017-07-10 21:00 ` Khem Raj
2017-07-10 21:09 ` Denys Dmytriyenko
2017-07-10 21:25 ` Khem Raj
[not found] ` <1499722526.27415.1.camel@pbcl.net>
2017-07-10 22:07 ` [Openembedded-architecture] " Denys Dmytriyenko
2017-07-10 22:16 ` Khem Raj
2017-07-10 22:22 ` Denys Dmytriyenko
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=20170710203642.GB26405@denix.org \
--to=denis@denix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox