From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: undef SHARED, and refactoring dynlink.c
Date: Sun, 15 Nov 2015 23:05:55 -0500 [thread overview]
Message-ID: <20151116040554.GP3818@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151115004942.GA31291@brightrain.aerifal.cx>
On Sat, Nov 14, 2015 at 07:49:42PM -0500, Rich Felker wrote:
> As part of the same project, since the dlstart.c code does not belong
> in libc.a and thus not in src/*, I'd like to move it to crt/rcrt1.c,
> and then have ldso/dlstart.c include ../crt/rcrt1.c, with some macros
> defined to adapt it to act as the dynamic linker entry point. This
> reverses the current direction of inclusion and makes the preprocessor
> logic less messy, I think.
I'll probably omit this change. I tried it and it didn't simplify
anything and perhaps made some of the preprocessor logic uglier.
Rich
prev parent reply other threads:[~2015-11-16 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 0:49 Rich Felker
2015-11-16 4:05 ` Rich Felker [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=20151116040554.GP3818@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).