Fellows,
I'm not sure where to put "-Wl,-m64" but setting CFLAGS, FFLAGS,
CXXFLAGS or LFDLAFS to "-Wl,-m64" always fails the lamtest configure
at
.
.
.
checking whether mpif77 accepts -g... yes
checking for ranlib... ranlib
checking for mpi.h... yes
checking for MPI_Initialized in -lmpi... no
configure: error: cannot continue -- cannot find MPI_Initialized
A "-Wc,-m64" choice fails the configure even earlier at
.
.
.
checking build system type... sparc-sun-solaris2.9
checking host system type... sparc-sun-solaris2.9
checking for mpicc... yes
checking for gcc... mpicc
checking for C compiler default output file name... configure: error: C compiler
cannot create executables
See `config.log' for more details.
I'm beginning to wonder if the warning from configuring lamtest I
reported has anything to do with the failling of lamtest execution I
complained about. After all, "make" works just fine in lamtest
without "-Wl," or "-Wc," and all executables created are
"ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked,
not stripped" files and an "ldd" on them finds all corresponding
64 bit libraries.
And I don't think libtool ignores "-m64" since without it in ??FLAGS
configure also fails.
Meanwhile, my LAM-MPI application is compiling and running just
fine with 64 bit.
I'm a newbe here but it seems to me that the problem, if any, resides
in lamtest for sparcv9 or in libtool as Ralf says.
So, I guess, I'll rest my case.
Finally, I ran a "make check" on every sub-directory of lamtest and got 5 fails
(with lamnodes: n0 supercomp:2:origin,this_node).
I'll leave it to you guys.
Best regards,
Alex
(Sorry fot the long output....)
1) attrsetget_f in lamtest/comm
mpirun -x TEST -s h C -ssi rpi crtcp /usr/local/lamtests-7.1.1/comm/./attrsetget_f
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 0, file attrsetget.c:66:
Getting attribute failed from within a C function
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file attrsetget.c:66:
Getting attribute failed from within a C function
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 28655 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h C -ssi rpi lamd /usr/local/lamtests-7.1.1/comm/./attrsetget_f
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 0, file attrsetget.c:66:
Getting attribute failed from within a C function
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file attrsetget.c:66:
Getting attribute failed from within a C function
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 28677 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h C -ssi rpi sysv /usr/local/lamtests-7.1.1/comm/./attrsetget_f
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 0, file attrsetget.c:66:
Getting attribute failed from within a C function
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file attrsetget.c:66:
Getting attribute failed from within a C function
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 28701 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h C -ssi rpi tcp /usr/local/lamtests-7.1.1/comm/./attrsetget_f
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 0, file attrsetget.c:66:
Getting attribute failed from within a C function
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file attrsetget.c:66:
Getting attribute failed from within a C function
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 28725 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h C -ssi rpi usysv /usr/local/lamtests-7.1.1/comm/./attrsetget_f
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 0, file attrsetget.c:66:
Getting attribute failed from within a C function
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file attrsetget.c:66:
Getting attribute failed from within a C function
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 28749 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
2) range in lamtest/group
mpirun -x TEST -s h -np 8 -ssi rpi crtcp /usr/local/lamtests-7.1.1/group/./range
mpirun -x TEST -s h -np 8 -ssi rpi lamd /usr/local/lamtests-7.1.1/group/./range
mpirun -x TEST -s h -np 8 -ssi rpi sysv /usr/local/lamtests-7.1.1/group/./range
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 29150 (MPI_COMM_WORLD rank: 1)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 29148 (MPI_COMM_WORLD rank: 0)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 29154 (MPI_COMM_WORLD rank: 3)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29148 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h -np 8 -ssi rpi tcp /usr/local/lamtests-7.1.1/group/./range
mpirun -x TEST -s h -np 8 -ssi rpi usysv /usr/local/lamtests-7.1.1/group/./range
3) spawn_appschema in lamtest/lam/dynamic
mpirun -x TEST -s h N -np 3 -ssi rpi crtcp
/usr/local/lamtests-7.1.1/lam/dynamic/./spawn_appschema
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 2, file spawn_appschema.c:92:
ERROR: MPI_Comm_spawn returned errcode = 2752517
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29450 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h N -np 3 -ssi rpi lamd
/usr/local/lamtests-7.1.1/lam/dynamic/./spawn_appschema
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29474 failed on node n0 (10.0.0.4) due to signal 11.
-----------------------------------------------------------------------------
mpirun -x TEST -s h N -np 3 -ssi rpi sysv
/usr/local/lamtests-7.1.1/lam/dynamic/./spawn_appschema
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29502 failed on node n0 (10.0.0.4) due to signal 11.
-----------------------------------------------------------------------------
mpirun -x TEST -s h N -np 3 -ssi rpi tcp
/usr/local/lamtests-7.1.1/lam/dynamic/./spawn_appschema
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 2, file spawn_appschema.c:92:
ERROR: MPI_Comm_spawn returned errcode = 2752517
[**ERROR**]: LAM/MPI MPI_COMM_WORLD rank 1, file spawn_appschema.c:92:
ERROR: MPI_Comm_spawn returned errcode = 2752517
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29531 failed on node n0 (10.0.0.4) due to signal 11.
-----------------------------------------------------------------------------
mpirun -x TEST -s h N -np 3 -ssi rpi usysv
/usr/local/lamtests-7.1.1/lam/dynamic/./spawn_appschema
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 29559 failed on node n0 (10.0.0.4) due to signal 11.
-----------------------------------------------------------------------------
FAIL: spawn_appschema
4) cart in lamtest/topo
mpirun -x TEST -s h -np 6 -ssi rpi crtcp /usr/local/lamtests-7.1.1/topo/./cart
mpirun -x TEST -s h -np 6 -ssi rpi lamd /usr/local/lamtests-7.1.1/topo/./cart
mpirun -x TEST -s h -np 6 -ssi rpi sysv /usr/local/lamtests-7.1.1/topo/./cart
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 214 (MPI_COMM_WORLD rank: 2)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 210 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h -np 6 -ssi rpi tcp /usr/local/lamtests-7.1.1/topo/./cart
mpirun -x TEST -s h -np 6 -ssi rpi usysv /usr/local/lamtests-7.1.1/topo/./cart
FAIL: cart
5) sub in lamtest/topo
mpirun -x TEST -s h -np 6 -ssi rpi crtcp /usr/local/lamtests-7.1.1/topo/./sub
mpirun -x TEST -s h -np 6 -ssi rpi lamd /usr/local/lamtests-7.1.1/topo/./sub
mpirun -x TEST -s h -np 6 -ssi rpi sysv /usr/local/lamtests-7.1.1/topo/./sub
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 733 (MPI_COMM_WORLD rank: 1)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
The selected RPI failed to initialize during MPI_INIT. This is a
fatal error; I must abort.
This occurred on host supercomp (n0).
The PID of failed process was 735 (MPI_COMM_WORLD rank: 2)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
One of the processes started by mpirun has exited with a nonzero exit
code. This typically indicates that the process finished in error.
If your process did not finish in error, be sure to include a "return
0" or "exit(0)" in your C code before exiting the application.
PID 730 failed on node n0 (10.0.0.4) with exit status 1.
-----------------------------------------------------------------------------
mpirun -x TEST -s h -np 6 -ssi rpi tcp /usr/local/lamtests-7.1.1/topo/./sub
mpirun -x TEST -s h -np 6 -ssi rpi usysv /usr/local/lamtests-7.1.1/topo/./sub
FAIL: sub
> * Martin Siegert wrote on Thu, Nov 10, 2005 at 01:47:30AM CET:
>>
>> the problem is usually that a libtool ignores the -m64 flag; in my
>> experience even if LDFLAGS include that flag.
>
> We've fixed that now in libtool.
>
>> You can check that by
>> finding the corresponding libtool line that leads to the make error:
>>
>> libtool --mode=link gcc -m64 -o ...
>>
>> usually leads to something like
>>
>> gcc -shared -o ...
>>
>> i.e., the gcc command following the libtool line is missing the -m64
>> flag. The only way that I found to work around this is to edit libtool
>> directly after you ran configure.
>
> No, you can use "-Wl," to pass options through libtool to the linker if
> the linker is $LD, or "-Wc," to pass them through libtool if the linker
> is $CC. This is unfortunately a bit inconsistent, but should work.
>
> In any case, this will be fixed in 1.5.22.
>
> Cheers,
> Ralf
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
|
