[ewg] OFED-1.4.1 build error in openmpi on RHEL5.3

Alexander Schmidt alexs at linux.vnet.ibm.com
Mon Mar 16 07:18:39 PDT 2009


Hi,

I am trying to compile the OFED daily build (OFED-1.4.1-20090312-0600) on RHEL
5.3, where I hit the following build error in openmpi:

gcc -DHAVE_CONFIG_H -I. -I.. -I../tools/opari/lib -I../extlib/otf/otflib -I../extlib/otf/otflib     -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mminimal-toc -m64 -g -O2 -D_GNU_SOURCE -DBINDIR=\"/usr/mpi/gcc/openmpi-1.3.1rc4/bin\" -DDATADIR=\"/usr/mpi/gcc/openmpi-1.3.1rc4/share\" -DRFG  -DVT_MEMHOOK -DVT_IOWRAP  -m64 -O2 -MT rfg_filter.o -MD -MP -MF .deps/rfg_filter.Tpo -c -o rfg_filter.o rfg_filter.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]: *** Waiting for unfinished jobs....
mv -f .deps/vt_comp_gnu.Tpo .deps/vt_comp_gnu.Po
mv -f .deps/rfg_regions.Tpo .deps/rfg_regions.Po
mv -f .deps/rfg_filter.Tpo .deps/rfg_filter.Po
make[5]: Leaving directory `/var/tmp/OFED_topdir/BUILD/openmpi-1.3.1rc4/ompi/contrib/vt/vt/vtlib'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/var/tmp/OFED_topdir/BUILD/openmpi-1.3.1rc4/ompi/contrib/vt/vt'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/var/tmp/OFED_topdir/BUILD/openmpi-1.3.1rc4/ompi/contrib/vt/vt'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/OFED_topdir/BUILD/openmpi-1.3.1rc4/ompi/contrib/vt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/OFED_topdir/BUILD/openmpi-1.3.1rc4/ompi'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.76004 (%build)

This has already been reported here:
http://www.open-mpi.org/community/lists/devel/2009/01/5230.php

According to the mail, removing the -D_FORTIFY_SOURCE=2 flag from the spec file
works around the issue, will this be done for the next RCs?

I appreciate your comments.

Alex



More information about the ewg mailing list