i386 architecture of input fille is incompatible with i386:x86-64 output

Questions regarding the compilation of VASP on various platforms: hardware, compilers and libraries, etc.


Moderators: Global Moderator, Moderator

Locked
Message
Author
zdhlover
Newbie
Newbie
Posts: 2
Joined: Thu Aug 26, 2010 10:56 am
License Nr.: 5-652

i386 architecture of input fille is incompatible with i386:x86-64 output

#1 Post by zdhlover » Thu Aug 26, 2010 12:19 pm

Hi,when teacher make the vasp,we encount a problem:

This is the make vasp log:
fftmpi.f90(714): (col. 16) remark: LOOP WAS VECTORIZED.
./preprocess <fftmpi_map.F | /usr/bin/cpp -P -C -traditional >fftmpi_map.f90 -DMPI -DHOST=\"LinuxIFC\" -DIFC -Dkind8 -DCACHE_SIZE=4000 -DPGF90 -Davoidalloc -DNGZhalf -DMPI_BLOCK=8000 -DRPROMU_DGEMV -DRACCMU_DGEMV
mpiifort -FR -lowercase -assume byterecl -O3 -axW -c fftmpi_map.f90
./preprocess <fftw3d.F | /usr/bin/cpp -P -C -traditional >fftw3d.f90 -DMPI -DHOST=\"LinuxIFC\" -DIFC -Dkind8 -DCACHE_SIZE=4000 -DPGF90 -Davoidalloc -DNGZhalf -DMPI_BLOCK=8000 -DRPROMU_DGEMV -DRACCMU_DGEMV
mpiifort -FR -lowercase -O1 -c fftw3d.f90
./preprocess <fft3dlib.F | /usr/bin/cpp -P -C -traditional >fft3dlib.f90 -DMPI -DHOST=\"LinuxIFC\" -DIFC -Dkind8 -DCACHE_SIZE=4000 -DPGF90 -Davoidalloc -DNGZhalf -DMPI_BLOCK=8000 -DRPROMU_DGEMV -DRACCMU_DGEMV
mpiifort -FR -lowercase -O2 -c fft3dlib.f90
fft3dlib.f90(4876): (col. 10) remark: PARTIAL LOOP WAS VECTORIZED.
fft3dlib.f90(1499): (col. 10) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1505): (col. 10) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1510): (col. 10) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1472): (col. 10) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(635): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1321): (col. 12) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1321): (col. 12) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1321): (col. 12) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(1294): (col. 12) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(504): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(504): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(505): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(506): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(270): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(271): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(272): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(82): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(83): (col. 15) remark: LOOP WAS VECTORIZED.
fft3dlib.f90(84): (col. 15) remark: LOOP WAS VECTORIZED.
./preprocess <main.F | /usr/bin/cpp -P -C -traditional >main.f90 -DMPI -DHOST=\"LinuxIFC\" -DIFC -Dkind8 -DCACHE_SIZE=4000 -DPGF90 -Davoidalloc -DNGZhalf -DMPI_BLOCK=8000 -DRPROMU_DGEMV -DRACCMU_DGEMV
mpiifort -FR -lowercase -assume byterecl -FR -O0 -c main.f90
rm -f vasp
mpiifort -o vasp main.o base.o mpi.o smart_allocate.o xml.o constant.o jacobi.o main_mpi.o scala.o asa.o lattice.o poscar.o ini.o xclib.o xclib_grad.o radial.o pseudo.o mgrid.o gridq.o ebs.o mkpoints.o wave.o wave_mpi.o wave_high.o symmetry.o symlib.o lattlib.o random.o nonl.o nonlr.o nonl_high.o dfast.o choleski2.o mix.o hamil.o xcgrad.o xcspin.o potex1.o potex2.o constrmag.o cl_shift.o relativistic.o LDApU.o paw_base.o metagga.o egrad.o pawsym.o pawfock.o pawlhf.o rhfatm.o paw.o mkpoints_full.o charge.o dipol.o pot.o dos.o elf.o tet.o tetweight.o hamil_rot.o steep.o chain.o dyna.o sphpro.o us.o core_rel.o aedens.o wavpre.o wavpre_noio.o broyden.o dynbr.o rmm-diis.o reader.o writer.o tutor.o xml_writer.o brent.o stufak.o fileio.o opergrid.o stepver.o chgloc.o fast_aug.o fock.o mkpoints_change.o sym_grad.o mymath.o internals.o dimer_heyden.o dvvtrajectory.o vdwforcefield.o hamil_high.o nmr.o force.o pead.o subrot.o subrot_scf.o pwlhf.o gw_model.o optreal.o davidson.o electron.o rot.o electron_all.o shm.o pardens.o paircorrection.o optics.o constr_cell_relax.o stm.o finite_diff.o elpol.o hamil_lr.o rmm-diis_lr.o subrot_cluster.o subrot_lr.o lr_helper.o hamil_lrf.o elinear_response.o ilinear_response.o linear_optics.o linear_response.o setlocalpp.o wannier.o electron_OEP.o electron_lhf.o twoelectron4o.o ratpol.o screened_2e.o wave_cacher.o chi_base.o wpot.o local_field.o ump2.o bse.o acfdt.o chi.o sydmat.o fftmpi.o fftmpi_map.o fftw3d.o fft3dlib.o /opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a -L../vasp.5.lib -ldmy ../vasp.5.lib/linpack_double.o -L/opt/intel/mkl/10.0.5.025/lib/em64t -lmkl_em64t -lguide -lpthread
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(dfftw_destroy_plan.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(dfftw_execute.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(dfftw_plan_dft_3d.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(fftw_destroy_plan.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(fftw_execute.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(fftw_plan_dft_3d.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(tt_fftw_in_to_out.o)' is incompatible with i386:x86-64 output
ld: i386 architecture of input file `/opt/intel/mkl/10.0.5.025/lib/em64t/libfftw3xf_intel.a(tt_fftw_norm.o)' is incompatible with i386:x86-64 output
make: *** [vasp] Error 1


how could we solve the problem?

Thanks a lot!
Last edited by zdhlover on Thu Aug 26, 2010 12:19 pm, edited 1 time in total.

support_vasp
Global Moderator
Global Moderator
Posts: 1817
Joined: Mon Nov 18, 2019 11:00 am

Re: i386 architecture of input fille is incompatible with i386:x86-64 output

#2 Post by support_vasp » Wed Sep 04, 2024 12:33 pm

Hi,

We're sorry that we didn’t answer your question. This does not live up to the quality of support that we aim to provide. The team has since expanded. If we can still help with your problem, please ask again in a new post, linking to this one, and we will answer as quickly as possible.

Best wishes,

VASP


Locked