(Illustration by Gaich Muramatsu)
Instead of doing this, I modified configure.in in coda: Index: configure.in =================================================================== RCS file: /coda-src/coda/configure.in,v retrieving revision 4.78 diff -c -r4.78 configure.in *** configure.in 2000/09/23 19:45:25 4.78 --- configure.in 2001/01/06 12:18:30 *************** *** 84,89 **** --- 84,90 ---- dnl Checks for compiler characteristics. CODA_CC_FEATURE_TEST(no_exceptions, -fno-exceptions) CODA_CXX_FEATURE_TEST(no_exceptions, -fno-exceptions) + CODA_CXX_FEATURE_TEST(no_operator_names, -fno-operator-names) dnl Checks for library functions. AC_CHECK_FUNCS(inet_aton inet_ntoa) -tim On Saturday, January 6, 2001, at 04:11 AM, Timothy J. Wood wrote: > > > The version of g++ that I'm using seems to obey some stupid C++ rule > where 'or' and 'and', etc' are operators. If you don't add > '-fno-operator-names' to the CFLAGS before configuring in the coda > directory, you'll get errors in coda-src/resolution/compops.cc > > The configure.in should probably check if this flag is understood and > if so, add it to the list of flags to use. > > -tim >Received on 2001-01-06 07:18:48