Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3BE9A656.12CAB9DD@ece.gatech.edu>
Date: Wed, 07 Nov 2001 16:23:34 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
CC: Corinna Vinschen <cygwin-apps AT cygwin DOT com>
Subject: Re: Did I find an error in the current binutils or what???
References: <20011107131736 DOT U2965 AT cygbert DOT vinschen DOT de>
	 <3BE94852 DOT 8080303 AT ece DOT gatech DOT edu>
	 <20011107163919 DOT Y2965 AT cygbert DOT vinschen DOT de>
	 <3BE95990 DOT 2000308 AT ece DOT gatech DOT edu>
	 <20011107175722 DOT A2965 AT cygbert DOT vinschen DOT de> <4 DOT 3 DOT 1 DOT 2 DOT 20011107153531 DOT 02222750 AT pop DOT ma DOT ultranet DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

"Larry Hall (RFK Partners, Inc)" wrote:
> 
> At 03:26 PM 11/7/2001, Charles Wilson wrote:
> > > Which is kinda mess since there's even no header on Linux which
> > > defines __progname.  Is there _any_ standard on where to define
> > > __progname?
> >
> >Hmm...it looks like __progname is a BSDism -- and I saw stuff where THEY
> >were complaining that it wasn't declared in system headers.  Apparently,
> >the "standard" is to declare "extern char * __progname" in your own code
> >-- which makes portable __declspec'ing difficult, unless we do something
> >ugly like:
> >
> >#ifdef CYGWIN
> >extern __declspec(dllimport) char * __progname;
> >#else
> >extern char * __progname;
> >#fi
> >
> >in all client code that wants __progname.  Or, just make sure folks use
> >new compilers and live with the "warning" about auto-import.
> 
> Assuming it's easy to turn off the auto-import warning (and only this
> warning), I'd say the latter is the best approach.

Actually, no -- it's a hardcoded warning for now.  We wanted to leave it
for a while, until the auto-import stuff settled down.  Removing (or
changing the priority of) those warnings is a topic for another thread.

--Chuck