1.5.0 - showstopper?

[Corinna Vinschen]

On Mon, Jul 07, 2003 at 02:41:22AM -0400, Charles Wilson wrote:
> >On Sun, Jul 06, 2003 at 06:24:58PM -0400, Charles Wilson wrote:
> >>But, thanks to the new magic in the headers, is it possible that certain 
> >>symbols (like open, fopen, etc) do not get listed as "_imp__foo" in the 
> >>import lib, but are actually thunked to "foo" in the static portion of 
> >>the import lib?
> >
> >I think I've fixed the cygwin magic that creates the aliased functions
> >such that replaced objects like "open" and "fopen" now look like other,
> >normal import objects.  It seems to fix this problem in a simple test
> >case, anyway.
> >[...]
> So, okay...
> 
> But I still think libcygwin.a should be added to the exlude libs list.  :-)

I'm curious, does that still make sense now?  Should libcygwin.a be added
to that list or is the problem ultimativly fixed by adding the appropriate
symbols to libcygwin.a?  Somehow I'm missing the conclusion in this
discussion.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.