This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


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

Re: Did I find an error in the current binutils or what???


"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


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