[OMPI users] BLACS Tester installation errors

2006-09-21 Thread Benjamin Gaudio
I have installed OpenMPI 1.1.1 for the first time yesterday and am
now having trouble getting the BLACS Tester to install properly. 
OpenMPI seemed to build without error, and BLACS also built without
any apparent errors.  When I tried to install the Blacs tester, one
of the first lines of output was:

g77: unrecognized option `-Nx400'

So, I tried removing it from Bmake.inc so that it read:

   F77NO_OPTFLAGS = 

which results in several "warnings" and also ends in rather
uninformative errors.  

I am very new to MPI / BLACS, so please forgive me if I am
overlooking something obvious.  

Here is some system information:
SUSE 10.1
g77 fortran compiler (does the same thing with gfortran)
openmpi 1.1.1

Attached is the output from both attempts, with the -Nx400 and
without.

Benjamin Gaudio


blacstester-output.tar.gz
Description: Binary data


Re: [OMPI users] BLACS Tester installation errors

2006-09-21 Thread Åke Sandgren
On Thu, 2006-09-21 at 09:26 -0400, Benjamin Gaudio wrote:
> I have installed OpenMPI 1.1.1 for the first time yesterday and am
> now having trouble getting the BLACS Tester to install properly. 
> OpenMPI seemed to build without error, and BLACS also built without
> any apparent errors.  When I tried to install the Blacs tester, one
> of the first lines of output was:

To compile blacstest with g77 you need
-fugly-complex -fno-globals -Wno-globals
Add this to TESTING/Makefile
where it compiles blacstest.

blacstest.o : blacstest.f
$(F77) -fugly-complex -fno-globals -Wno-globals
$(F77NO_OPTFLAGS) -c $*.f

-- 
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet: a...@hpc2n.umu.se   Phone: +46 90 7866134 Fax: +46 90 7866126
Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se



[OMPI users] sed: command garbled:

2006-09-21 Thread Lydia Heck

I am trying to build openmpi-1.1.2 for Solaris x86/64 with the studio11
compilers and including the mx drivers. I have gone past some hurdles.
However when the configure script nears its end where Makefiles are prepared
I get error messages of the form:

config.status: creating ompi/mca/osc/rdma/Makefile
sed: command garbled: s,@OMPI_CXX_ABSOLUTE@,/opt/studio11/SUNWspro/bin/CC
sed: command garbled: s,@OMPI_F90_ABSOLUTE@,/opt/studio11/SUNWspro/bin/f95
sed: command garbled: s,@OMPI_CC_ABSOLUTE@,/opt/studio11/SUNWspro/bin/cc
config.status: creating ompi/mca/pml/cm/Makefile


This is with the system's sed command.

I have tried to use the
gnu sed command and get instead


sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
config.status: creating orte/Makefile
sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
config.status: creating orte/include/Makefile
sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
config.status: creating orte/etc/Makefile
sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
config.status: creating orte/tools/orted/Makefile
sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command



Is there anything I do overlook?

Lydia



Re: [OMPI users] sed: command garbled:

2006-09-21 Thread Lydia Heck


My apologies I forgot to attach the config.log file.


On Thu, 21 Sep 2006, Lydia Heck wrote:

>
> I am trying to build openmpi-1.1.2 for Solaris x86/64 with the studio11
> compilers and including the mx drivers. I have gone past some hurdles.
> However when the configure script nears its end where Makefiles are prepared
> I get error messages of the form:
>
> config.status: creating ompi/mca/osc/rdma/Makefile
> sed: command garbled: s,@OMPI_CXX_ABSOLUTE@,/opt/studio11/SUNWspro/bin/CC
> sed: command garbled: s,@OMPI_F90_ABSOLUTE@,/opt/studio11/SUNWspro/bin/f95
> sed: command garbled: s,@OMPI_CC_ABSOLUTE@,/opt/studio11/SUNWspro/bin/cc
> config.status: creating ompi/mca/pml/cm/Makefile
>
>
> This is with the system's sed command.
>
> I have tried to use the
> gnu sed command and get instead
>
>
> sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
> sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
> config.status: creating orte/Makefile
> sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
> sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
> config.status: creating orte/include/Makefile
> sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
> sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
> config.status: creating orte/etc/Makefile
> sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
> sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
> config.status: creating orte/tools/orted/Makefile
> sed: file ./confstatlmaOTV/subs-3.sed line 31: unterminated `s' command
> sed: file ./confstatlmaOTV/subs-4.sed line 4: unterminated `s' command
>
>
>
> Is there anything I do overlook?
>
> Lydia
>
>

--
Dr E L  Heck

University of Durham
Institute for Computational Cosmology
Ogden Centre
Department of Physics
South Road

DURHAM, DH1 3LE
United Kingdom

e-mail: lydia.h...@durham.ac.uk

Tel.: + 44 191 - 334 3628
Fax.: + 44 191 - 334 3645
___

openmpi-config.log.gz
Description: config.log of attempted configuration


Re: [OMPI users] linux alpha ev6 openmpi 1.1.1

2006-09-21 Thread Nuno Sucena Almeida
Actually,

I got curious and checked it myself, and to my surprise the $31 had 
disappeared , so i searched a bit and realized that I need to add escape 
characters to $ because of m4, and so I did:

OMPI_GCC_INLINE_ASSIGN='"bis [$]31,[$]31,%0" : "=&r"(ret)'


both to alpha-*)  and  alphaev6-*)

but now, although configure reports that gcc supports inline 
assembly:

checking if gcc supports GCC inline assembly... yes   <--
checking if gcc supports DEC inline assembly... no
checking if gcc supports XLC inline assembly... no
checking if g++ supports GCC inline assembly... yes <--

it says that it cannot generate atomic operations, since it 
lacks a 
ALPHA.asm:

checking for pre-built assembly file... no (not in asm-data)
checking whether possible to generate assembly file... failed
configure: WARNING: Could not build atomic operations assembly file.
configure: WARNING: There will be no atomic operations for this build.
checking for atomic assembly filename... none

but it continues the configure process. 
I start compiling and I get another error:


al_object.c  -fPIC -DPIC -o class/.libs/opal_object.o
opal_object.s: Assembler messages:
opal_object.s:445: Error: syntax error
opal_object.s:446: Error: bad expression
opal_object.s:446: Error: syntax error
opal_object.s:447: Error: bad expression
opal_object.s:447: Error: syntax error
opal_object.s:448: Error: bad expression
opal_object.s:448: Error: syntax error
opal_object.s:449: Error: syntax error
opal_object.s:450: Error: bad expression
opal_object.s:450: Error: syntax error
opal_object.s:451: Error: junk at end of line, first unrecognized character is 
`/'
opal_object.s:452: Error: bad expression
opal_object.s:452: Error: syntax error
opal_object.s:522: Error: syntax error
opal_object.s:523: Error: bad expression
opal_object.s:523: Error: syntax error
opal_object.s:524: Error: bad expression
opal_object.s:524: Error: syntax error
opal_object.s:525: Error: bad expression
opal_object.s:525: Error: syntax error
opal_object.s:526: Error: syntax error
opal_object.s:527: Error: bad expression
opal_object.s:527: Error: syntax error
opal_object.s:528: Error: junk at end of line, first unrecognized character is 
`/'
opal_object.s:529: Error: bad expression
opal_object.s:529: Error: syntax error
make[2]: *** [class/opal_object.lo] Error 1
make[2]: Leaving directory `/usr/src/mpi/openmpi-1.1.1/opal'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/mpi/openmpi-1.1.1/opal'
make: *** [all-recursive] Error 1
(...)


, but beware that I'm using the gcc flag '-save-temps' to check where 
the 
problem was:

make CFLAGS=-save-temps

so I started searching where that macro might come from and ended up in
opal/include/opal/sys/alpha/atomic.h
I took out the extra //  comments in the asm code from
 'opal_atomic_cmpset_32' and opal_atomic_cmpset_64'  which seemed to 
fix that 
problem and restarted the compilation and after some more compiling it bombed 
out in:

(...)
then mv -f "$depbase.Tpo" "$depbase.Plo"; else rm -f "$depbase.Tpo"; exit 1; 
fi
gcc -DHAVE_CONFIG_H -I. -I. -I../opal/include -I../orte/include 
-I../ompi/include -I../ompi/include -I.. -save-temps -MT 
class/opal_object.lo -MD -MP -MF class/.deps/opal_object.Tpo -c 
class/opal_object.c  -fPIC -DPIC -o class/.libs/opal_object.o
opal_object.s: Assembler messages:
opal_object.s:734: Error: can't resolve `.rodata' {.rodata section} - `L0' 
{.text section}
opal_object.s:734: Error: can't resolve `.text' {.text section} - `L0' 
{.rodata section}
make[2]: *** [class/opal_object.lo] Error 1
make[2]: Leaving directory `/usr/src/mpi/openmpi-1.1.1/opal'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/mpi/openmpi-1.1.1/opal'
make: *** [all-recursive] Error 1
(...)

and here I got stuck :)

I send my config.log in the attachment, with just the bis [$]31 
modification

Regards,

Nuno




On Sunday 17 September 2006 19:01, Brian Barrett wrote:
> > (...)
> > gcc -O3 -DNDEBUG -fno-strict-aliasing -pthread -o .libs/opal_wrapper
> > opal_wrapper.o -Wl,--export-dynamic  ../../../opal/.libs/libopal.so
> > -ldl -lnsl -lutil -lm -Wl,--rpath -Wl,/opt/openmpi-1.1.1/lib
> > ../../../opal/.libs/libopal.so: undefined reference to
> > `opal_atomic_cmpset_acq_32'
> > ../../../opal/.libs/libopal.so: undefined reference to
> > `opal_atomic_cmpset_32'
> > (...)
>
> Can you send the config.log file generated by Open MPI's configure,
> with your bis $31,$31 change?

-- 
http://aeminium.org/slug/

*
** **
** WARNING:  This email contains an attachment of a very suspicious type.  *