From: William Tambe <tambewilliam@gmail.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: ld -shared support
Date: Sun, 23 Feb 2020 20:44:00 -0000 [thread overview]
Message-ID: <CAF8i9mPVHahWqpGWin0-+RWADiqaU08dsceuWVtR87M+YOLH0g@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mNhEb6_2dvQF_Vjw0AyO92R4u7t2yR0gT02ajwhHYrgJg@mail.gmail.com>
I am now able to use ld -shared after using:
GENERATE_SHLIB_SCRIPT=yes
However when compiling a test shared library using:
gcc -shared -o test.so test.c
The following error occur:
crt0.o: error adding symbols: no error
The linker is successfully able to open crt0.o printing the following
when using -verbose:
attempt to open crt0.o succeeded
Any idea what might be missing ?
On Sat, Feb 22, 2020 at 11:02 PM William Tambe <tambewilliam@gmail.com> wrote:
>
> What needs to be done to support -shared in the link-editor ?
>
> Is there a commit that describe how to support -shared ?
next prev parent reply other threads:[~2020-02-23 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 4:02 William Tambe
2020-02-23 20:44 ` William Tambe [this message]
2020-02-25 17:14 ` William Tambe
2020-02-27 13:24 ` William Tambe
2020-03-02 17:28 ` Nick Clifton
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=CAF8i9mPVHahWqpGWin0-+RWADiqaU08dsceuWVtR87M+YOLH0g@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).