From: "Ian Lance Taylor via binutils" <binutils@sourceware.org>
To: Marian Kechlibar <marian.kechlibar@circletech.net>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: GOLD linker and arm-none-symbianelf
Date: Mon, 20 Feb 2017 18:44:00 -0000 [thread overview]
Message-ID: <CAKOQZ8zFC=CbNMw0Gfk8Lu2GmmqBiGXYkm4=u+jPDSssmhXk8w@mail.gmail.com> (raw)
In-Reply-To: <0d1821cb-04b3-584a-a8c0-73a271158626@circletech.net>
On Mon, Feb 20, 2017 at 9:16 AM, Marian Kechlibar
<marian.kechlibar@circletech.net> wrote:
>
> although Symbian OS is practically dead in the commercial world, I still
> have to support several hundred Symbian OS - based clients.
>
> Recently, I successfully built binutils 2.27 for target
> arm-none-symbianelf. It works. But I cannot build "gold" for this
> target, only "ld". It seems that the target platform is not supported.
>
> I can build gold for linux from the same sources just fine.
>
> Is really gold unusable on arm-none-symbianelf?
>
> If I still wanted to build gold for arm-none-symbianelf, what edits do I
> have to do in config/makefiles in order to get the system to build the
> binary?
What is different between arm-none-elf and arm-none-symbianelf, and
how do does differences affect the linker?
If there is no effect on the linker then you probably just need to
edit the handling of ENABLE_GOLD in the top-level configure.ac to
recognize "symbianelf" as identical to "elf".
Looking at ld/emulparams/armsymbian.sh, though, and comparing it to
ld/emulparams/armelf.sh, it looks like some special symbols may need
to be defined. That will require more work.
Ian
next prev parent reply other threads:[~2017-02-20 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 17:17 Marian Kechlibar
2017-02-20 18:44 ` Ian Lance Taylor via binutils [this message]
2017-02-20 18:51 ` Marian Kechlibar
2017-02-20 20:27 ` Ian Lance Taylor via binutils
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='CAKOQZ8zFC=CbNMw0Gfk8Lu2GmmqBiGXYkm4=u+jPDSssmhXk8w@mail.gmail.com' \
--to=binutils@sourceware.org \
--cc=iant@google.com \
--cc=marian.kechlibar@circletech.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).