From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Linker and duplicate symbols
Date: Fri, 2 Sep 2016 18:12:09 +0200 [thread overview]
Message-ID: <a6eb846133f99a5ca5e65996ee55426a@felloff.net> (raw)
In-Reply-To: <9B2C4ECD-E92C-4C76-8678-74E26DBCD1CD@yahoo.ca>
uses the first one it finds, so the order matters. its not unusual
for programs to override certain library function by providing ther
own version and putting them first in the object file list. this
works only when the function you want to replace sits alone in his
own object file (the smallest unit of linkage).
the kernel does link in some standard libc functions, but obviously
not the ones attempting syscalls :)
--
cinap
next prev parent reply other threads:[~2016-09-02 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 2:34 Chris McGee
2016-09-02 10:20 ` Richard Miller
2016-09-02 15:56 ` Chris McGee
2016-09-02 16:11 ` Richard Miller
2016-09-09 0:48 ` Chris McGee
2016-09-09 8:31 ` Richard Miller
2016-09-09 14:55 ` Chris McGee
2016-09-09 16:37 ` Richard Miller
2016-09-02 16:12 ` cinap_lenrek [this message]
2016-09-02 20:00 ` Chris McGee
2016-09-02 22:34 ` Steve Simon
2016-09-03 16:58 ` Chris McGee
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=a6eb846133f99a5ca5e65996ee55426a@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.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 NNTP newsgroup(s).