> Pavel Pavlov <pavel@xxxxxxxxxxxxxx> writes: > > > In that particular case I have this config.status : > > http://pastebin.com/PSsaya6F Yet, the final config.h is absolutely identical to > config.in: http://pastebin.com/ecL4qkqT with the only change added is the > single line at the top: > > /* config.h. Generated from config.in by configure. */ > > There is some contradiction there. The config.status file says HAVE_LIMITS_H > should be defined. The config.h file says that it is not defined. > > Precisely which config.status and config.h file did you paste? There are several > different files with those names in the build tree. In particular, did you paste > files from the same directory? > > The most useful file to look at in these cases is the config.log file. > Look at the one in the directory whose config.h says that HAVE_LIMITS_H is > undefined. Look for the test for whether limits.h is present. Look for > compilation errors. [Pavel Pavlov] These are the file that are used. That's clearly a contradiction, definitely some tools are buggy that transform config.in to config.h. I opened config.in converted it to UNIX style line endings and re-run configure and now config.h matches whatever is in config.status. I have no idea how someone managed to break autotools so badly that it can't split CRLF delimited text by LF only. Even if it treated CR as some character then still it should have produced correct results. I forced svn line endings to LF now, I never had problems with line endings in Windows/VS tools, but that's not the first time I get that problem in *nix related builds, so I set svn to always use LF to make Cygwin et al happy.
