autoconf test failures - how to react?

2006-05-03 Thread Jerker Bäck
Hello autoconf users I have build autoconf-2.59c (ftp source) for Interix and the build process went on with no problems. When I run 'make check' some tests fails. Please help me to evaluate the seriosness of these failed tests. ERROR: 272 tests were run, 8 failed (5 expected failures). 7 tests we

Re: autoconf test failures - how to react?

2006-05-04 Thread Jerker Bäck
Thanks for the replies My apologies for the duplicate posts - I became impatient when the post didn't show up, sorry for that. > A nice system to test on. Actually, only GNU m4 1.4.4 should > be necessary. Do things change if you use the BSD sed and > make, instead of GNU sed and GNU make? Yes,

Re: autoconf test failures - how to react?

2006-05-07 Thread Jerker Bäck
> 225: AC_TYPE_INT64_TWindows NT Exception (core dumped) > That's an interesting diagnostic. I suspect this come from GNU sed since it disappear with BSD sed I need to recompile sed more carefully > 12: autoupdating AC_PREREQ FAILED (tools.at:570) > makes it look like the Perl

Re: autoconf test failures - how to react?

2006-05-09 Thread Jerker Bäck
> Looks like you forgot quotes. Try > $ perl 'system("echo foo | /bin/m4")' Thanks Eric $ perl -e 'system("echo foo | /bin/m4")' foo $ I take it the test results are basically OK and the paket can be used as is. As Interix is based on BSD it would be interesting to see how it compares to other B

SV: autoconf test failures - how to react?

2006-05-09 Thread Jerker Bäck
> IMVHO we can ignore failures that are obviously due to system-specific > bugs in Interix tools, unless someone can provide us with a good analysis, > enabling a decent workaround. I've posted the failed results in the /tools forum at Interop Systems Hopefully - eventually - a good analysis can r

AC_FUNC_SETVBUF_REVERSED - shouldn't it be the other way around?

2006-11-27 Thread Jerker Bäck
Hello all, The AC_FUNC_SETVBUF_REVERSED macro seems to be fairly common and used in a number of tools (ex GNU make). The macro always fails to test the MS compiler resulting in the wrong "#define SETVBUF_REVERSED 1", but succeed in testing gcc. In this case, both compilers are using the same C-libr

Version defines in config.h

2006-12-07 Thread Jerker Bäck
Is there a way to get the following defines to be written to config.h during configure? #define FILEVERSION_MAJOR 1 #define FILEVERSION_MINOR 2 #define FILEVERSION_RELEASE 3 #define FILEVERSION_BUILD 1 #define FILEVERSION_BETA0// TRUE 1 or FAL