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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20011107153531.02222750@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 07 Nov 2001 15:36:26 -0500 To: Charles Wilson , Corinna Vinschen From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Did I find an error in the current binutils or what??? In-Reply-To: <3BE998DF.82555DDE@ece.gatech.edu> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX