Re: [AMBER-Developers] compile errors

From: case <case.biomaps.rutgers.edu>
Date: Thu, 25 Feb 2010 22:04:07 -0500

On Thu, Feb 25, 2010, Jason Swails wrote:
>
> A fresh checkout of Amber11 is giving the following errors when
> compiled with intel compilers and intel MKL (linux em64t):

Sigh...I am really looking forward to changing to git. There have been
something like 75 CVS commits today, so saying something like "a fresh
checkout of Amber11" is only mildly helpful. Once we make the change, you
can specify an exact commit that I can be sure to reproduce.

>
> 18:38:07 [linx64: ~] > ifort -V
> Intel(R) Fortran Compiler for applications running on Intel(R) 64,
> Version 10.1 Build 20080312 Package ID: l_fc_p_10.1.015
> Copyright (C) 1985-2008 Intel Corporation. All rights reserved.
>
> 18:38:25 [linx64: ~] > icc -V
> Intel(R) C Compiler for applications running on Intel(R) 64, Version
> 10.1 Build 20080312 Package ID: l_cc_p_10.1.015
> Copyright (C) 1985-2008 Intel Corporation. All rights reserved.
>
> 18:39:44 [linx64: ~] > echo $MKL_HOME
> /opt/intel/mkl/10.0.2.018/


Be sure you have again done "cvs co"; be sure you have re-configured; then
post your config.h file (if the problem persists). We particularly need to
see what your FLIBS variable is.

> /ufl/qtp/aer/gps/arwen_3/amber11/bin/nab -o matgen matgen.o

Another idea: go to amber11/src/nss and type "nab -v matgen.o". That will
give verbose output that should help locate the problem.

> /ufl/qtp/aer/gps/arwen_3/amber11/lib/libnab.a(pbsaapi.o)(.text+0x271):
> In function `prepb_read_':
> : undefined reference to `for_write_seq_lis'

The entry point should be defined in libifcore.a in the library connected
to your ifort compiler. For me, this is in /opt/intel/fce/10.1.018/lib.
So either your FLIBS variable doesn't have "-ifcore" in it, or it's in the
wrong order, or the compiler is not looking in the proper directory, or....

>
> What's strange is that I did not get this error with the version 11
> intel compilers (though this is a separate checkout by someone else in
> our group, but it's new nonetheless).
>

I don't see that there has been any change in the location of
for_write_seq_lis between version 10 and 11 of ifort. Also, things work for
me for both verion 10.1.025 and 11.1. So, I'm hoping that you just got
trapped in an inconsitent CVS state.

....dac

_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Feb 25 2010 - 19:30:03 PST
Custom Search