From: Pedro Alves <pedro_alves@portugalmail.pt>
To: binutils@sourceware.org
Subject: Re: environ is autofiltered from dll export list?
Date: Wed, 24 May 2006 14:33:00 -0000 [thread overview]
Message-ID: <447457D9.8050202@portugalmail.pt> (raw)
In-Reply-To: <04d701c67f2d$e3c433a0$a501a8c0@CAM.ARTIMI.COM>
Dave Korn wrote:
> On 23 May 2006 22:02, Pedro Alves wrote:
>
>
>> Also, while looking at it, why are _fmode, _impure_ptr,
>> cygwin_attach_dll, cygwin_premain0, cygwin_premain1, cygwin_premain2,
>> cygwin_premain3 and environ in the autofilter_symbolprefixlist[] instead
>> of the autofilter_symbollist[]? Probably an oversight.
>>
>
> Actually, it really suggests that "cygwin_premain" should be in the prefix
> list. The others should probably move to the symbol list as you suggest.
>
>
Ok, I can provide a patch for that, but I would like to understand the
environ part of my question first.
> char** environ is explicitly disabled from dll exporting in
pe-dll.c's autofilters. Why is it? I tried to look in the archives,
> back when the auto-importing was introduced, but couldn't find the
rationale.
> Should every dll have its own environ?
I think this was needed when there was no auto-importing, and cygwin
defined environ as __cygwin_environ:
http://www.zsh.org/mla/workers/2000/msg03158.html
Is it still needed? In that case I will have to conditionally compile
out that part for arm-wince-pe target.
Cheers,
Pedro Alves
next prev parent reply other threads:[~2006-05-24 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 7:38 Pedro Alves
2006-05-24 13:38 ` Dave Korn
2006-05-24 14:33 ` Pedro Alves [this message]
2006-05-25 1:18 ` Christopher Faylor
2006-05-25 3:18 ` Dave Korn
2006-05-25 22:49 ` Pedro Alves
2006-06-23 12:16 ` Nick Clifton
2006-06-23 14:01 ` Pedro Alves
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=447457D9.8050202@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--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).