AMBER Archive (2006)

Subject: Re: AMBER: amber9 serial compile with pathscale on SuSe10.1/AMD64

From: David A. Case (case_at_scripps.edu)
Date: Fri Nov 24 2006 - 18:43:20 CST

On Fri, Nov 24, 2006, In Hee Park wrote:
>
> While I was trying to serial compile amber9(cd-rom version) with
> bugfix.all patched up to now using pathscale2.5 compiler on AMD64
> machine running on SuSe10.1-novell, I noticed that only 31 executables
> were created out of 61 executables if successful compile completion.

Note the the compilation script stops at the *first* error, so any executables
that would be compiled after that will not get built. The workaround is to
comment out things that aren't working, so that the rest can get built.

Here is the error (at the bottom of your message):

pathCC -c -o elsize.o elsize.cc
In file included from /usr/include/c++/4.1.0/string:52,
                 from /usr/include/c++/4.1.0/bits/locale_classes.h:47,
                 from /usr/include/c++/4.1.0/bits/ios_base.h:47,
                 from /usr/include/c++/4.1.0/ios:48,
                 from /usr/include/c++/4.1.0/istream:44,
                 from /usr/include/c++/4.1.0/fstream:44,
                 from elsize.cc:74:
/usr/include/c++/4.1.0/bits/basic_string.h: In member function `bool
   std::basic_string<_CharT, _Traits, _Alloc>::_M_disjunct(const _CharT*)
const
   ':
/usr/include/c++/4.1.0/bits/basic_string.h:329: error: parse error before `;'
   token
make[1]: *** [elsize.o] Error 1

For some reason, pathCC is not able to compile a header that is being included
from the elsize program. You could look at line 329 of
/usr/include/c++/4.1.0/bits/basic_string.h to see if anything obvious is going
on. Note that this is not inside the Amber code, but in a system header file.

First, elsize is an extremely specialized program (I've never run it myself),
so you can pretty safely comment out the line in etc/Makefile that creates
this; If you really need it, compile with g++ rather than pathCC.

Second, someone from the Virginia Tech crowd should look into this. I don't
think there is any real reason why the elsize program should be a C++ program
anyway. I know we have talked about conversion to C, but don't remember if
anything happened.

...good luck...dac

-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber_at_scripps.edu
To unsubscribe, send "unsubscribe amber" to majordomo_at_scripps.edu