hi David,
Thanks for your answer. I was just trying to recreate the error so I could type it here. Here's the full bit:
cc -DCC='"cc"' -DCPP='"ucpp -l"' -DFLIBS='"-lsff_mpi -lpbsa -larpack -llapack -lblas -L/ccs/home/zty/codes/amber12/lib -lnetcdf -lgfortran -w "' \
-DBINTRAJ -DMPI \
-o /ccs/home/zty/codes/amber12/bin/mpinab nab.c
/ccs/home/zty/codes/amber12/bin/mpinab -c allatom_to_dna3.nab
make: *** [allatom_to_dna3.o] Illegal instruction
as far as the static flag: we need static executables to run on the crays…and the cray flag helps with the cray compiler wrappers…
FF
On Jul 18, 2012, at 1:02 PM, David A Case wrote:
> On Wed, Jul 18, 2012, Foertter, Fernanda S. wrote:
>>
>> I'm trying to help a user compile Amber12 on Jaguar here at ORNL and I
>> keep getting stuck at a nab2c test.
>>
>> I get the errors below:
>>
>> ~/codes/amber12/AmberTools/src/nab> ../../bin/mpinab2c -c -v dna3.nab
>> nab2c: Internal error: nfname required
>
> We need more context: the above command is not supposed to work, and you would
> need a "-nfname" flag, as the error message indicates. So the question is:
> how was the command created? Is it a part of the "make" process? What was
> happening before this?
>
> [One oddity is that, as far as I can see, Amber12 Makefiles never refer to
> "../../bin" anymore, but but use the full path to $AMBERHOME instead. So I'm
> looking for more information about what commands you typed, and maybe the full
> log the make process.]
>
>>
>> amber12/bin/mpinab -v -c allatom_to_dna3.nab
>> Illegal instruction
>>
>> my flags are: ./configure -crayxt5 -nomtkpp -static -noX11 -mpi gnu
>
> This looks harder. Can you try removing the -crayxt5 and -static flags?
>
> ....dac
>
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Wed Jul 18 2012 - 11:00:03 PDT
