[Pkg-openmpi-maintainers] [Fwd: Bug#657625: FTBFS openmpi 1.5 (experimental) on armel]

[Jeffrey Squyres]

On Feb 25, 2012, at 1:23 PM, Sylvestre Ledru wrote:

>> I'm fine with the idea of Debian not building openmpi for (armv4t) armel. But would it be possible to include it in Ubuntu armel builds anyway?
> In Debian, we are providing both armel & armhf (v7). If we drop armel support in OpenMPI packages,
> we will have to switch back a lot of packages to mpich2 (for the armel arch).

Ick.  That's unattractive to me.

> Since 1.4 is still recommended over the 1.5, I think Debian will stick with the 1.4 for Wheezy.
> I will see later if we are going to package the 1.5 as a different package like our Ubuntu's friends just did.

FWIW, v1.5.5 is just about to come out, and it's going to be the final release in the 1.5 series, and then we'll transition to 1.6 (which will replace 1.4).

What's your timeline for wheezy?

> Anyway, thanks for your work and your answers!
> Sylvestre
> PS: While I am chatting with upstream devs, are you familiar with this
> issue with openmpi 1.4.5 ?
> 
> /bin/sh ../../../libtool --tag=CC   --mode=link gcc  -DNDEBUG -Wall -g
> -O2 -finline-functions -fno-strict-aliasing -pthread -fvisibility=hidden
> -export-dynamic   -o orte-checkpoint
> orte-checkpoint.o ../../../orte/libopen-rte.la -lnsl -lutil  -lm 
> libtool: link: gcc -DNDEBUG -Wall -g -O2 -finline-functions
> -fno-strict-aliasing -pthread -fvisibility=hidden
> -o .libs/orte-checkpoint orte-checkpoint.o
> -Wl,--export-dynamic  ../../../orte/.libs/libopen-rte.so -lnsl -lutil
> -lm -pthread -Wl,-rpath -Wl,/usr/lib/openmpi/lib
> /usr/bin/ld: orte-checkpoint.o: undefined reference to symbol
> 'opal_class_initialize'
> /usr/bin/ld: note: 'opal_class_initialize' is defined in
> DSO /home/sylvestre/dev/debian/openmpi/branches/openmpi-1.4.5/build/shared/opal/.libs/libopen-pal.so.0 so try adding it to the linker command line
> /home/sylvestre/dev/debian/openmpi/branches/openmpi-1.4.5/build/shared/opal/.libs/libopen-pal.so.0: could not read symbols: Invalid operation
> 
> with
> ../../configure --build i486-linux-gnu --with-ft=cr --with-blcr=/usr
> --with-blcr-libdir=/usr/lib --with-libnuma=/usr
> --with-libnuma-libdir=/usr/lib --with-devel-headers
> --enable-heterogeneous --with-tm


That doesn't sound familiar.  I can't imagine how libopen-pal.so.0 could have unreadable symbols.  Is your build arch different than your host arch?  This might not be something we have tested well.

-- 
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/