Re: GCC4 status.

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Feb 25 17:30, Dave Korn wrote:
> Corinna Vinschen wrote:
> 
> > #1)
> > 
> >   sftp.c:368: warning: 'opterr' redeclared without dllimport attribute:
> >   previous dllimport ignored
> > 
> >   Yes, well, so what?
> 
>   This one IIRC has some significance.  If you declare any extern symbols at
> all with dllimport attributes, it disables auto-import altogether.  So a stray
> definition like that can break linking all the other functions that would
> normally be auto-imported.

So why does it do that at all: "previous dllimport ignored"?
It shouldn't do that.  The dllimport should have precedence, IMHO.

> > #2)
> > 
> >   /usr/lib/gcc/i686-pc-cygwin/4.3.2/../../../../i686-pc-cygwin/bin/ld:
> >   warning: auto-importing has been activated without --enable-auto-import
> >   specified on the command line.
> >   This should work unless it involves constant data structures referencing
> >   symbols from auto-imported DLLs.
> > 
> >   *Sob*  Yes, officer, I confess everything!  But *please* don't tell
> >   me this every time I dare to link an application.
> > 
> > Is there any chance to get rid of this really useless stuff upstream?
> 
>   I don't know.  We could turn on auto import globally but that will pessimize
> a whole bunch of stuff that needn't be affected.  We could discard the warning
> altogether but then people would get silent failures.

I think auto import should be the default.  You don't have this problem
and the message on any other platform.  Why isn't the default setting so
that we get what other platforms get, too?  I never had the case so far
where auto import would have hurt.  Am I just maintaining too simple
projects?

>   As a workaround, the sources could always be fixed.  Inconsistent
> declarations *is* a correctness issue, after all, and it's usually trivial to
> add an item to LDFLAGS.

There's only so much platform uglification put up with in the upstream
OpenSSH sources...

>   Also, perhaps as a half-way compromise measure, auto import could be enabled
> in the GCC specs for just C++/ObjC++/Java.  I don't know what's for the best
> yet, does anyone else have any suggestions?

...which are written in plain C, btw.  So this compromise is none
for a lot of packages in the Cygwin distro, not only for OpenSSH.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat