The ABINIT Users Mailing List ( CLOSED )

["Vivek Ranjan" <vranjan@ncsu.edu>]

Hi,

Thank you. There was very little progress. It did compile a bit and then
stopped. I used the following in "b1n1.ac" file :

###############################################################
fc_type="ibm"
fc_version="9.1"
#FC=mpxlf
#FC=mpxlf_r
#FC=mpxlf90_r
#C=mpcc
#C=mpcc_r
#FFLAGS=-O3 -q64 -qarch=auto -qtune=auto -qstrict -qsuffix=f=f90
#CFLAGS=-O3 -q64 -qstrict
#FFLAGS=-O3 -qarch=auto -qtune=auto -qstrict -qsuffix=f=f90
#CFLAGS=-O3 -qstrict
#AR_COMMAND= ar -Xany
###############################################################

I tried different options. No options other than the first two lines above
work. Even in this case, I get an error message early during compilation.
The error message is :

---------------------------------------------------------------------------
        /usr/bin/ar -X64 cru liblight.a module.o aluminum.o dens.o 
embedd.o ener.o enerpot.o  forc.o inicell.o inipos.o  inivel.o
lightweight.o move_li.o  output.o readinput.o screen.o 
testforce.o v.o

ar: 0707-126 module.o is not valid with the current object file mode.
        Use the -X option to specify the desired object mode.
---------------------------------------------------------------------------

Then I tried to use "AR_COMMAND= ar -Xany", but I get the same message,
because of the first two lines. Can you please suggest something please ?
How can I get abinit-5.2 ?

Thank you,
Vivek





> Hi,
>
> The build system is not sensitive to Fortran compiler names. Yet, in
> version 5.1 of ABINIT, there are still some issues related to XLF. They
> have been fixed in version 5.2.
>
> With version 5.1, using "mpxlf" or "mpxlf_r" as compiler name should do.
> If not, you may add the following lines to your config file:
>
> fc_type="ibm"
> fc_version="9.1"
>
> Please note that this is a quick and *VERY* dirty fix, which is no more
> needed with ABINIT 5.2.
>
> Best regards,
>
> Yann.
>
> Le mercredi 19 juillet 2006 à 10:04 +0200, Damien Caliste a écrit :
>
>> You're using xlf90, aren't you? This compiler uses non standard options
>> and this annoys the build system. To avoid that, Yann Pouillon added a
>> wrapper around that compiler. The build system will activate this
>> wrapper according to the name of your compiler. So use an alias to
>> ensure the compiler name to 'xlf90' (without _r).
>> When you run 'configure', in the Fortran support section, you should
>> have two lines like these ones :
>> checking if we are using the IBM XL Fortran compiler... yes
>> configure: applying Fortran compiler tricks (type: ibm, version: 9.1)
>>
>> Damien.
>>
>
>


__________________________________________________________________________
web : http://www.geocities.com/vivekranjanweb
__________________________________________________________________________
Vivek Ranjan                             Email : vranjan@chips.ncsu.edu
Center for High Performance Simulation         : vranjan@ncsu.edu
Department of Physics
NC State University                      Phone : +1-919-513-0613 (Office)
Campus Box 7518                          Fax   : +1-919-513-4804
Raleigh, NC 27695
--------------------------------------------------------------------------