search for: posixly

...cking for fpclassify... no checking for fpclassify with <math.h>... yes checking for finite... yes checking for isinf... yes checking if IEEE math works out of the box... yes Resolve Portability Issues checking if realloc can deal with NULL... yes checking if ctime_r need special care to act posixly correct... no checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads w...

Hi all, Recently there''s been discussion [1] in the Linux community about how filesystems should deal with rename(2), particularly in the case of a crash. ext4 was found to truncate files after a crash, that had been written with open("foo.tmp"), write(), close() and then rename("foo.tmp", "foo"). This is because ext4 uses delayed allocation and may not