On Monday, April 15, 2002, at 02:19 PM, Edward Avis wrote:
>>> Another problem I found was the use of deprecated headers. Instead of >>> <foo.h> newer compilers would prefer you to use <foo> and then access >>> the 'std' namespace explicitly. >> Yes, and lots of people have older compilers that don't like the <foo> >> notation. > But anyway, the actual bug is just with the configure script. That's exactly my point. You want to fix the configure script, but I'm pretty sure that people with gcc-2.8.x (and certainly 2.7.x, which there are plenty) and vendor-supplied compilers will have the "fixed" configure script fail with that change. > Yes, maybe the best option is to have configure just ignore the compiler > warning when testing for the presence of <fstream.h>. This is easier said than done without crafting your own autoconf macro. An easier solution is to try one form, then if it fails, try the other. -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
