cygwin-1.3.11-20020609 snapshot: mark_closed() complains when building the cygwin1.dll

[Nicholas Wourms]

Pavel,

I can confirm this when running configure scripts on Windows ME when I had
compiled cygwin1.dll with --enable-debugging.  So the question is, does
this message indicate a potential issue?

Cheers,
Nicholas

--- Pavel Tsekov <ptsekov@syntrex.com> wrote:
> Please, see the attached file for more information. Search for
> "mark_closed" to find where it starts to complain since the
> uncompressed log is around 700 kb.
> 
> I don't know if this is a way to reproduce, but still, here are the
> steps
> i've taken (i think this may not be a problem which shows up every
> time):
> 
> 1. patched the 20020609 snapshot to 20020610.
> 2. patched newlib with the sexec* removal patch (from newlib maling
> list)
> 3. rm -rf * the object directory
> 4. CFLAGS=-g CXXFLAGS=-g ../configure --enable-debugging
> 5. make
> 6. CTRL+C at some place when newlib was built
> 7. make clean
> 8. make
> 
> uname -a
> CYGWIN_NT-5.1 MORDOR 1.3.11s(0.53/3/2) 20020609 00:55:38 i686 unknown
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/