On Sat, Jul 02, 2005, Hal Rosenstock <[EMAIL PROTECTED]> wrote: > mstflint doesn't build on x86_64. Here is the version of g++: > g++ -v > Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.2/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --disable-libunwind-exceptions --enable-languages=c,c++,objc,java,f77 > --enable-java-awt=gtk --host=x86_64-redhat-linux > Thread model: posix > gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
It's not an x86-64 problem, it's a C++ problem. mstflint uses NULL where it should be using 0 for the function protoytypes in the class definitions. Older gcc versions were a bit more lenient, but it has tightened up to meet the C++ specs recently. I just recently ran into this problem and I have a patch, but it's at the office. If someone doesn't get around to it before Tuesday, I'll send it in. JE _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
