[mvapich-discuss] Linking problems

Jonathan Perkins perkinjo at cse.ohio-state.edu
Tue Jun 22 12:18:41 EDT 2010


There have been many improvements, both performance and bug fixes, to
mvapich2 since the 1.2 release.  I suggest updating to our latest
release mvapich2-1.5rc2 to take advantage of these.

The issue at hand doesn't appear to be related to mpi but due to
linking fortran and c objects together.  I suggest using the icc
compiler to do the linking with the -nofor_main option.  This should
remove the error message that you're seeing about main being multiply
defined.  Let us know if this solves your problem.

On Tue, Jun 22, 2010 at 11:02 AM, J R Jones <j.jones at bath.ac.uk> wrote:
> Hi
>
> This is the output at present.  I'll run it again with the -show option
> shortly when the machine is less busy..  I also couldn't see anything
> explicit in the scripts so I don't know if perhaps it is something to do
> with our Intel Compiler.  I've built GotoBLAS2 with the Intel compilers
> for 64-bit with the default options, and am now trying to build HPL-2.0
> using the same compilers, the built GotoBLAS2 and MVAPICH2.  I am aware
> however that this is using version 1.2 as supplied by our cluster vendor
> so I don't know if this is something that has been fixed.
>
> mpif77 -DAdd_ -DF77_INTEGER=int -DStringSunStyle
> -I/home/jrj24/blas/hpl-2.0/include
> -I/home/jrj24/blas/hpl-2.0/include/Linux_Intel_FBLAS_gm
> -fomit-frame-pointer -O3 -funroll-loops -W -Wall -o
> /home/jrj24/blas/hpl-2.0/bin/Linux_Intel_FBLAS_gm/xhpl HPL_pddriver.o
>      HPL_pdinfo.o           HPL_pdtest.o
> /home/jrj24/blas/hpl-2.0/lib/Linux_Intel_FBLAS_gm/libhpl.a
> /home/jrj24/blas/goto/lib/standard/libgoto2.a
> ifort: command line remark #10148: option '-W' not supported
> ifort: command line warning #10156: ignoring option '-W'; no argument
> required
> HPL_pddriver.o: In function `main':
> ../HPL_pddriver.c:(.text+0x0): multiple definition of `main'
> /cm/shared/apps/intel/Compiler/11.1/046/lib/intel64/for_main.o:/export/users/nbtester/efi2linux_nightly/branch-ubs-11_1/20090701_000000/libdev/frtl/src/libfor/for_main.c:(.text+0x0):
> first defined here
> ld: Warning: size of symbol `main' changed from 80 in
> /cm/shared/apps/intel/Compiler/11.1/046/lib/intel64/for_main.o to 2224
> in HPL_pddriver.o
> /cm/shared/apps/intel/Compiler/11.1/046/lib/intel64/libimf.so: warning:
> warning: feupdateenv is not implemented and will always fail
> /cm/shared/apps/intel/Compiler/11.1/046/lib/intel64/for_main.o: In
> function `main':
> /export/users/nbtester/efi2linux_nightly/branch-ubs-11_1/20090701_000000/libdev/frtl/src/libfor/for_main.c:(.text+0x38):
> undefined reference to `MAIN__'
>
> Many thanks
>
> Jess
>
> On 22/06/10 15:58,, Jonathan Perkins wrote:
>> Hi, I just double checked and I don't see any explicit use of ld in
>> any of these wrapper scripts.  These should just be executing ifort
>> and icc directly for both the compilation and linking steps.  Can you
>> send some output displaying the commands?  Try adding the -show (or
>> the more extreme -echo) option when using mpif77 to get more verbose
>> information.
>>
>> On Tue, Jun 22, 2010 at 6:21 AM, J R Jones <j.jones at bath.ac.uk> wrote:
>>> Is there a way to configure mpif77 to use ifort for linking (and mpicc
>>> to use icc)?  It keeps defaulting to using ld and this is causing errors
>>> as they aren't entirely compatible.
>>>
>>> Many thanks
>>>
>>> Jess
>>> _______________________________________________
>>> mvapich-discuss mailing list
>>> mvapich-discuss at cse.ohio-state.edu
>>> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>>
>>>
>>
>>
>>
>
>



-- 
Jonathan Perkins



More information about the mvapich-discuss mailing list