On 12.02.2015 12:12, kay wrote: > These are the three config's files that I found. > > -rw-r--r-- 1 sptest1 sptest1 7856 Feb 11 11:40 svn_private_config.h > -rw-r--r-- 1 sptest1 sptest1 7263 Dec 8 19:26 svn_private_config.h.in > -rw-r--r-- 1 sptest1 sptest1 3195 Nov 23 2012 svn_private_config.hw
Well, somehow the compiler is including a file called svn_private_config.h, but that file doesn't contain at least two macros that it should. This is obvious from your 'make' logs: * the file is found, otherwise the compiler would emit an error about a missing include file; * these macros that should be (and, by your own words, are) in that file are not defined: o the missing #define _(x) causes the large number of int-to-pointer conversion warnings; o the missing SVN_PATH_LOCAL_SEPARATOR causes it to compile a code path that it absolutely should not be compiling on your platform, and then error out due to the undefined symbol. There are only two possible causes for this that I can think of: 1. your system (disk, caches, RAM, whatever) is broken in such a way that you see the contents of svn_private_config.h but the compiler doesn't; 2. you have another svn_private_config.h file somewhere in the include path that does not define those two macros. Of the above, cause #2 seems far more likely. Note that, in normal circumstances, a Subversion build should be free of warnings. This depends on platforms, and I'm not counting the bindings, but if you're seeing a lot of warnings in your build, you can assume that something is wrong with your build setup. -- Brane