Dear Sir.

I changed the single quotes around the brackets by double quotes in the atom.f 
file.
Then I compile it. There is no error when copiling the atom.f file. But at last 
it occures
error as following:
ifort -o siesta \
..........
..........
/opt/intel/mkl721/lib/em64t/libmkl_lapack.a: could not read symbols: File 
format not recognized
make: *** [siesta]  Error1.

The software and hardware I use as following:

l_fc_pc_8.1.024.tar
l_mkl_p_7.2.1.003.tar
Redhat Linux As
IBM X236 I06  cpu Xeon 3.2 em64t

Now how can I do?











>Dear Mingsu Si,
>
>   This problem was discussed previously in this forum. A simple 
>solution: Change the single quotes around the brackets by double quotes 
>and it probably it will compile successfully.
>
>Regards.-
>
>
>simingsu wrote:
>
>>Dear Mr Eduardo Anglada
>>
>>
>>I have just started to compile the SIESTA code with Intel ifort 8.1
>>compiler and MKL 7.2.1 libraries. The problem is that it is not able to
>>compile atom.f file. The errors printed out are given below:
>>
>>#####################################################################
>>ifort -c -w -mp -tpp7 -O3   atom.f
>>fortcom: Error: atom.f, line 4485: Unbalanced parentheses
>>
>>     .       nsm=1,nsemic(l)+1-(cnfigtb(l,nsemic(l)+1,is)-config(l)))
>>--------------------------------------------------------------------^
>>
>>fortcom: Error: atom.f, line 4484: Syntax error, found ',' when
>>expecting one of: :
>>
>>     .          (cnfigtb(l,nsm,is),sym(l),'(',qPAO(l,nsm),')',
>>----------------------------------^
>>
>>fortcom: Error: atom.f, line 4484: Syntax error, found ''' when
>>expecting one of: ( * :: , <IDENTIFIER> <CHAR_CON_KIND_PARAM>
>><CHAR_NAM_KIND_PARAM> <CHARACTER_CONSTANT> ...
>>
>>     .          (cnfigtb(l,nsm,is),sym(l),'(',qPAO(l,nsm),')',
>>----------------------------------------------------------^
>>
>>compilation aborted for atom.f (code 1)
>>make: *** [atom.o] Error 1
>>#####################################################################
>>
>>What can I do?
>>
>>Mingsu Si
>>Lanzhou University
>>June 10 2005
>>
>>
>>  
>>


Reply via email to