On Mon, Aug 13, 2007 at 08:04:39PM -0500, Dirk Eddelbuettel wrote: > On 14 August 2007 at 00:08, Adrian Knoth wrote: > | On Mon, Aug 13, 2007 at 04:26:31PM -0500, Dirk Eddelbuettel wrote: > | > | > > I'll now compile the 1.2.3 release tarball and see if I can reproduce > | > | The 1.2.3 release also works fine: > | > | adi@debian:~$ ./ompi123/bin/mpirun -np 2 ring > | 0: sending message (0) to 1 > | 0: sent message > | 1: waiting for message > | 1: got message (1) from 0, sending to 0 > | 0: got message (1) from 1 > > Now I'm even more confused. I though the bug was that it segfaulted when used > on a Debian-on-freebsd-kernel system ?
I think Adrian used a tarball, not the Debian package? I'll try a local, manual install too, maybe the bug is Debian-related only? > | adi@debian:~$ ./ompi123/bin/ompi_info > | Open MPI: 1.2.3 > | Open MPI SVN revision: r15136 > | Open RTE: 1.2.3 > | Open RTE SVN revision: r15136 > | OPAL: 1.2.3 > | OPAL SVN revision: r15136 > | Prefix: /home/adi/ompi123 > | Configured architecture: x86_64-unknown-kfreebsd6.2-gnu Same here. > | > | JFTR: It's currently not possible to compile OMPI on amd64 (out of the > | > | box). Though it compiles on i386 > | > | > | > | > http://experimental.debian.net/fetch.php?&pkg=openmpi&ver=1.2.3-3&arch=kfreebsd-i386&stamp=1187000200&file=log&as=raw > | > | > | > | it fails on amd64: > | > | > | > | > http://experimental.debian.net/fetch.php?&pkg=openmpi&ver=1.2.3-3&arch=kfreebsd-amd64&stamp=1186969782&file=log&as=raw > | > | > | > | stacktrace.c: In function 'opal_show_stackframe': > | > | stacktrace.c:145: error: 'FPE_FLTDIV' undeclared (first use in this > | > | function) > | > | stacktrace.c:145: error: (Each undeclared identifier is reported only > | > | once > | > | stacktrace.c:145: error: for each function it appears in.) > | > | stacktrace.c:146: error: 'FPE_FLTOVF' undeclared (first use in this > | > | function) > | > | stacktrace.c:147: error: 'FPE_FLTUND' undeclared (first use in this > | > | function) > | > | make[4]: *** [stacktrace.lo] Error 1 > | > | make[4]: Leaving directory `/build/buildd/openmpi-1.2.3/opal/util' > | > | > | > | > | > | This is caused by libc0.1-dev in /usr/include/bits/sigcontext.h, the > | > | relevant #define's are placed in an #ifdef __i386__ condition. After > | > | extending this for __x86_64__, everything works fine. > | > | > | > | Should I file a bugreport against libc0.1-dev or will you take care? > | > I'm confused. What is libc0.1-dev? > | > | > | http://packages.debian.org/unstable/libdevel/libc0.1-dev > | > | It's the "libc6-dev" for GNU/kFreeBSD, at least that's how I understand > | it. > > I see, thanks. Well if the bug is in the header files supplied by that > package, please go ahead and file a bug report. I talked to Aurelien Jarno on IRC and he fixed this issue in svn (an updated libc0.1 package will soon be uploaded). I guess the openmpi Debian packages should then depend on the new, fixed version. I verified that with the fixed version openmpi compiles on kfreebsd-i386 and kfreebsd-amd64. > | If you follow my two links and read their headlines, you can see that > | these are the buildlogs of 1.2.3-3 on kfreebsd, working for i386, but > | failing for amd64. > | > | This is caused by "wrong" libc headers on kfreebsd, that's why I thought > | Uwe might want to have a look at it. > > Ok. Back to the initial bug of Open MPI on Debian/kFreeBSD. What exactly is > the status now? With the libc0.1 fix (and another small patch for Debian which I'll send soon) both the kfreebsd-i386 and kfreebsd-amd64 packages build fine. However, on my systems, both i386 and amd64 still segfault. I'm using the openmpi Debian packages, version 1.2.3-3. I'll try the stock tarballs soon, and/or wait for 1.2.4 to see if the bug is already fixed there... HTH, Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
signature.asc
Description: Digital signature
