From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH 2/3] Have different definitions of __pthread_tsd_main agree in size
Date: Mon, 11 Feb 2013 15:39:44 +0100 [thread overview]
Message-ID: <20130211143944.GF6181@port70.net> (raw)
In-Reply-To: <1360591648.9132.117.camel@eris.loria.fr>
* Jens Gustedt <jens.gustedt@inria.fr> [2013-02-11 15:07:28 +0100]:
> the current model there is even the danger that environ and __environ
> split into two different objects.
>
> char **environ;
>
> int main(void) {
> return (long)&environ;
> }
>
> When compile-linking this with musl I get both symbols environ and
> __environ linked in.
>
and that is precisely what posix requires
> So it would at least be good that the internal use of it in musl would
> be consistent and the C library would not see two distinct objects.
>
no
"The ISO C standard and this volume of POSIX.1-2008 do not conflict
on the use of environ, but some historical implementations of environ
may cause a conflict. As long as environ is treated in the same way
as an entry point (for example, fork()), it conforms to both standards.
A library can contain fork(), but if there is a user-provided fork(),
that fork() is given precedence and no problem ensues.
The situation is similar for environ: the definition in this volume of
POSIX.1-2008 is to be used if there is no user-provided environ to take
precedence. At least three implementations are known to exist that
solve this problem."
next prev parent reply other threads:[~2013-02-11 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 22:32 Jens Gustedt
2013-02-11 0:31 ` Rich Felker
2013-02-11 7:40 ` Jens Gustedt
2013-02-11 11:22 ` Szabolcs Nagy
2013-02-11 12:08 ` Szabolcs Nagy
2013-02-11 12:51 ` Jens Gustedt
2013-02-11 13:09 ` Szabolcs Nagy
2013-02-11 13:38 ` Jens Gustedt
2013-02-11 13:44 ` Rich Felker
2013-02-11 14:07 ` Jens Gustedt
2013-02-11 14:39 ` Szabolcs Nagy [this message]
2013-02-11 16:30 ` Jens Gustedt
2013-02-11 17:08 ` Szabolcs Nagy
2013-02-11 17:21 ` Jens Gustedt
2013-02-11 21:49 ` Rich Felker
2013-02-11 21:47 ` Rich Felker
2013-02-11 21:50 ` Rich Felker
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=20130211143944.GF6181@port70.net \
--to=nsz@port70.net \
--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).