Eric Blake | 26 Oct 2010 00:47
Picon
Favicon
Gravatar

older cygwin failures [was: bugs-Please see it once]

[please keep the list in the loop, and quit top-posting, or I will be 
unlikely to reply further]

On 10/25/2010 04:23 PM, Rajan Modi wrote:
>
> i m using ns 2.28

That doesn't help me.  I need to know what release of cygwin you are 
running on; the output of 'uname -a' and './build-aux/config.guess' are 
more valuable than telling me that you are trying to build ns 2.28.

>   and sir i am sending u the contents of log file..

Thank you.  These failures are all related to gnulib tests, so I'm 
adding the gnulib list in cc:.

> FAIL: test-fopen-safer.exe (exit: 134)
> ======================================
> test-fopen.h:48: assertion failed

That one is testing for a particular errno value from 
fopen("file/","r"), which should fail; older cygwin had a bug where it 
would mistakenly succeed, but current cygwin does not have this bug. 
Since cygwin is actively maintained, and more importantly, open source, 
it is more efficient for gnulib to focus only on current releases and 
fix bugs in cygwin itself, rather than maintaining lots of ports in 
gnulib to work around older cygwin bugs.  Therefore, my recommendation 
is to upgrade to the latest cygwin version rather than making packages 
like m4 install workarounds for bugs that have been fixed in the 
meantime.  The cygwin list is a better resource if you have questions on 
(Continue reading)


Gmane