Subject: Re: [OMPI users] Compile problems with 1.3.2
From: Jim Kusznir (jkusznir_at_[hidden])
Date: 2009-06-29 17:02:02
Ok, trying now. This does bring up a question I've been meaning to
ask. I need to find a way to analyze the efficiency of parallel jobs,
and the only way I've known about in the past is through vampire. I
do not have the software license presently (and last I looked, it was
a commercial licensed product). Does this configure flag suggest that
openmpi has native support for generating vampire trace files? Is
there any open source tools for analyzing them (or another route I
should be looking at)?
[presently many of our jobs are running with a very large "system CPU"
component. That has me concerned as to the efficiency of the overall
application. In general, I'd like to assess the overall efficiency of
the parallel application and identify areas to improve it.]
Thanks!
--Jim
On Mon, Jun 29, 2009 at 1:46 PM, Ralph Castain<rhc_at_[hidden]> wrote:
> Easiest solution: add -enable-contrib-no-build=vt to your configure line.
> This will "no-build" the Vampirtrace code section that is causing the
> problem. It isn't required for operations - just there as an option if you
> want it for debugging purposes.
>
> Ralph
>
>
> On Mon, Jun 29, 2009 at 2:31 PM, Jim Kusznir <jkusznir_at_[hidden]> wrote:
>>
>> Hi all:
>>
>> I'm trying to build and install openmpi-1.3.2 for my cluster using
>> enviornment-modules. My build failed, but on something that I have no
>> idea how to debug. Here's the relevent output:
>>
>> Making all in vtlib
>> make[5]: Entering directory
>> `/usr/src/redhat/BUILD/openmpi-1.3.2/ompi/contrib/vt/vt/vtlib'
>> gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib
>> -I../extlib/otf/otflib -I../extlib/otf/otflib -D_GNU_SOURCE
>> -DBINDIR=\"/opt/openmpi-gcc/1.3.2/bin\"
>> -DDATADIR=\"/opt/openmpi-gcc/1.3.2/share\" -DRFG -DVT_BFD -DVT_MEMHOOK
>> -DVT_IOWRAP -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT
>> vt_comp_gnu.o -MD -MP -MF .deps/vt_comp_gnu.Tpo -c -o vt_comp_gnu.o
>> vt_comp_gnu.c
>> mv -f .deps/vt_comp_gnu.Tpo .deps/vt_comp_gnu.Po
>> gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib
>> -I../extlib/otf/otflib -I../extlib/otf/otflib -D_GNU_SOURCE
>> -DBINDIR=\"/opt/openmpi-gcc/1.3.2/bin\"
>> -DDATADIR=\"/opt/openmpi-gcc/1.3.2/share\" -DRFG -DVT_BFD -DVT_MEMHOOK
>> -DVT_IOWRAP -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT
>> vt_memhook.o -MD -MP -MF .deps/vt_memhook.Tpo -c -o vt_memhook.o
>> vt_memhook.c
>> mv -f .deps/vt_memhook.Tpo .deps/vt_memhook.Po
>> gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib
>> -I../extlib/otf/otflib -I../extlib/otf/otflib -D_GNU_SOURCE
>> -DBINDIR=\"/opt/openmpi-gcc/1.3.2/bin\"
>> -DDATADIR=\"/opt/openmpi-gcc/1.3.2/share\" -DRFG -DVT_BFD -DVT_MEMHOOK
>> -DVT_IOWRAP -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT
>> vt_memreg.o -MD -MP -MF .deps/vt_memreg.Tpo -c -o vt_memreg.o
>> vt_memreg.c
>> mv -f .deps/vt_memreg.Tpo .deps/vt_memreg.Po
>> gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib
>> -I../extlib/otf/otflib -I../extlib/otf/otflib -D_GNU_SOURCE
>> -DBINDIR=\"/opt/openmpi-gcc/1.3.2/bin\"
>> -DDATADIR=\"/opt/openmpi-gcc/1.3.2/share\" -DRFG -DVT_BFD -DVT_MEMHOOK
>> -DVT_IOWRAP -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT
>> vt_iowrap.o -MD -MP -MF .deps/vt_iowrap.Tpo -c -o vt_iowrap.o
>> vt_iowrap.c
>> vt_iowrap.c:1242: error: expected declaration specifiers or '...'
>> before numeric constant
>> vt_iowrap.c:1243: error: conflicting types for '__fprintf_chk'
>> make[5]: *** [vt_iowrap.o] Error 1
>> make[5]: Leaving directory
>> `/usr/src/redhat/BUILD/openmpi-1.3.2/ompi/contrib/vt/vt/vtlib'
>>
>>
>> I used this as my build command:
>>
>> rpmbuild -bb --define 'install_in_opt 1' --define 'install_modulefile
>> 1' --define 'modules_rpm_name environment-modules' --define
>> 'build_all_in_one_rpm 0' --define 'configure_options
>> --with-tm=/opt/torque' --define '_name openmpi-gcc' openmpi-1.3.2.spec
>>
>> Suggestions?
>>
>> --Jim
>> _______________________________________________
>> users mailing list
>> users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>