Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: David Gunter (dog_at_[hidden])
Date: 2006-04-10 10:22:12


I've attached the config.log and configure output files. The OS on
the machine is

(flashc 119%) cat /etc/redhat-release
Red Hat Linux release 9 (Shrike)
(flashc 120%) uname -a
Linux flashc.lanl.gov 2.4.24-cm32lnxi6plsd2pcsmp #1 SMP Thu Mar 10
15:27:12 MST 2005 i686 athlon i386 GNU/Linux

-david


On Apr 10, 2006, at 7:55 AM, Brian Barrett wrote:

> On Apr 10, 2006, at 9:43 AM, David Gunter wrote:
>
>> After much fiddling around, I managed to create a version of open-mpi
>> that would actually build. Unfortunately, I can't run the simplest
>> of applications with it. Here's the setup I used:
>>
>> export CC=gcc
>> export CXX=g++
>> export FC=gfortran
>> export F77=gfortran
>> export CFLAGS="-m32"
>> export CXXFLAGS="-m32"
>> export FFLAGS="-m32"
>> export FCFLAGS="-m32"
>> export LDFLAGS="-L/usr/lib"
>
> That looks about right. I'm surprised you need the LDFLAGS, but I
> can see where it might be needed, and I doubt it's causing the
> problems you are seeing. Actually, mmm... depending on which LANL
> system you are on, that might be needed for gm, so that makes sense.
>
>> ./configure --prefix=/net/scratch1/dog/flash64/openmpi/
>> openmpi-1.0.2-32b --build=i686-pc-linux-gnu --with-bproc --with-g
>> m --enable-io-romio --with-romio --with-io-romio-flags='--build=i686-
>> pc-linux-gnu'
>
> I'm surprised you need the --build= flag, but again, not what is
> causing issues here.
>
>> Configure completes, as does 'make' and then 'make install'. Next I
>> tried to compile a simple MPI_Send test application, which fails to
>> run:
>>
>> (flashc 104%) gcc -m32 -I/net/scratch1/dog/flash64/openmpi/
>> openmpi-1.0.2-32b/include -o send4 send4.c -L/net/scratch1/dog/
>> flash64/openmpi/openmpi-1.0.2-32b/lib -lmpi
>> /net/scratch1/dog/flash64/openmpi/openmpi-1.0.2-32b/lib/libopal.so.0:
>> warning: epoll_wait is not implemented and will always fail
>> /net/scratch1/dog/flash64/openmpi/openmpi-1.0.2-32b/lib/libopal.so.0:
>> warning: epoll_ctl is not implemented and will always fail
>> /net/scratch1/dog/flash64/openmpi/openmpi-1.0.2-32b/lib/libopal.so.0:
>> warning: epoll_create is not implemented and will always fail
>
> That's extremely weird. For some reason, we're trying to use the
> epoll code, but it clearly isn't supported (as the linker so nicely
> informs us). I'm a little curious how this can happen. Would you
> mind sending the output of configure as well as the config.log file
> it generates? Also, do you know what OS is running on that machine?
>
> Thanks,
>
> Brian
>
>
> --
> Brian Barrett
> Open MPI developer
> http://www.open-mpi.org/
>
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users