From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11318 invoked by alias); 24 May 2006 16:20:36 -0000 Received: (qmail 11297 invoked by uid 22791); 24 May 2006 16:20:35 -0000 X-Spam-Check-By: sourceware.org Received: from pool-71-248-179-19.bstnma.fios.verizon.net (HELO cgf.cx) (71.248.179.19) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 May 2006 16:20:13 +0000 Received: by cgf.cx (Postfix, from userid 201) id 1485013C01F; Wed, 24 May 2006 12:20:12 -0400 (EDT) Date: Thu, 25 May 2006 01:18:00 -0000 From: Christopher Faylor To: Pedro Alves , binutils@sourceware.org Subject: Re: environ is autofiltered from dll export list? Message-ID: <20060524162012.GA25356@trixie.casa.cgf.cx> Mail-Followup-To: Pedro Alves , binutils@sourceware.org References: <04d701c67f2d$e3c433a0$a501a8c0@CAM.ARTIMI.COM> <447457D9.8050202@portugalmail.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447457D9.8050202@portugalmail.pt> User-Agent: Mutt/1.5.11 X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00442.txt.bz2 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