On Sun, Oct 05, 2014 at 07:58:34PM +0200, Gustaf Neumann wrote: > the NS_EXPORT situation is a mess, not being able to write to the > log file in an error situation is not really an option.
The way NS_EXPORT is defined twice, in two totally separate places, is indeed ugly, but AFAICT, after my one initial fix to it weeks ago, it hasn't actually had any impact on my attempts to get Naviserver working on Windows. > Rather than commenting out error messages, the better option is probably > to move the ns.h include to the end and add warning lines, since reentrant.c > contains no NS_EXTERN etc. AFAICT, it has NEVER worked to call Ns_Log from the reentrant.c file, not on Linux and not on Windows either. Never. Making it work would be nice, but is well out of scope of my current "fix Naviserver to it actually builds and runs on Windows" work. -- Andrew Piskorski <a...@piskorski.com> ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
