This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: environ is autofiltered from dll export list?


On Wed, May 24, 2006 at 01:55:53PM +0100, Pedro Alves wrote:
>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.

Are you asking if cygwin still exports environ as __cygwin_environ?  If
so, then the answer is "yes".

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]