From: Florian Weimer <fweimer@redhat.com>
To: "Y.D. via Libc-help" <libc-help@sourceware.org>
Subject: Re: Add a new function to dlfcn.h?
Date: Tue, 25 Aug 2020 14:46:52 +0200 [thread overview]
Message-ID: <87lfi27v0j.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAF6YOcOPKmHP0tJMOEEQyfZ6zEDABt1hZGcvsyct5V9xyvzvxA@mail.gmail.com> (Y. D. via Libc-help's message of "Mon, 17 Aug 2020 10:15:28 +0800")
* Y. D. via Libc-help:
> Now I've created a new file called dl-usage.c under elf/. And I've added
> dl-usage to routines in Makefile under elf/, just in case, I've added it to
> dl-routines, too.
One of my in-flight patches already uses elf/dl-usage.c, so you might
want to use something else:
<https://sourceware.org/pipermail/libc-alpha/2020-June/115258.html>
> But when I create a new file, including dlfcn.h and refer to the function,
> the error message is "undefined reference to `dlusage' collect2: error: ld
> returned 1 exit status".
You need to add it to elf/Versions under a new GLIBC_2.33 section,
otherwise the linker will treat it as a hidden symbol.
Thanks,
Florian
prev parent reply other threads:[~2020-08-25 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 12:52 Y.D.
2020-08-16 12:59 ` Florian Weimer
2020-08-17 2:15 ` Y.D.
2020-08-25 12:46 ` Florian Weimer [this message]
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=87lfi27v0j.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@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).