Hi Jan,
On 11/03/2016 09:14 PM, Jan Rheinländer wrote:
On 11/03/2016 12:13 PM, Jan Rheinländer wrote:
On 11/01/2016 09:59 PM, Jan Rheinländer wrote:
#include <unistd.h> trips up compilation with MSVC. Is it really required? I commented it out and the file compiled anyway. Where is the close() function declared, if not in <unistd.h>? good question - but as I said, if I just comment out <unistd.h> it compiles on MSVC and all checks pass successfully. So maybe it needs a conditional: Can you, please, try to find out where close() comes from on your system?
-richy. it's defined in <corecrt_io.h> which in turn is included by <io.h> Interesting. And which header includes <io.h>? (I'm sure you don't mean <cln/io.h>.) I can't really find anything. Maybe autoconf does some magic? Because in
Hi Richard, libtool and ltmain.sh it says: #ifdef _MSC_VER # include <direct.h> # include <process.h> # include <io.h> #else # include <unistd.h> # include <stdint.h> # ifdef __CYGWIN__ # include <io.h> # endif #endif Jan