On May 13, 2007, at 6:23 AM, Bert Wesarg wrote:
Even better: is there a patch available to fix this in the 1.2.1
tarball, so that
I can set the full path again with CC?
The patch is quite trivial, but requires a rebuild of the build
system
(autoheader, autoconf, automake,...)
see here:
htt
Hello,
Rob wrote:
> livelfs wrote:
>>
>> your 1.2.1 build error seems to be the one I bumped into.
>> Try to avoid to give an absolute path to CC macro when you run configure
>> (check the archives)
>
> Hmmm, to get a decent fortran compiler for my AlphaServers, I have to
> compile my own GCC com
livelfs wrote:
>
> your 1.2.1 build error seems to be the one I bumped into.
> Try to avoid to give an absolute path to CC macro when you run configure
> (check the archives)
Hmmm, to get a decent fortran compiler for my AlphaServers, I have to
compile my own GCC compiler set (the default with Cen
Rob wrote:
>
> Hi,
>
> One more question with respect to running OpenMPI on my AlphaServers
> and other PCs in my lab.
>
> Version 1.2.1 fails to build on the AlphaServers, but miraculously the
> nightly snapshot openmpi-1.3a1r14639 works fine. Now, I need to have
> OpenMPI set up on a production c
Hi,
One more question with respect to running OpenMPI on my AlphaServers
and other PCs in my lab.
Version 1.2.1 fails to build on the AlphaServers, but miraculously the
nightly snapshot openmpi-1.3a1r14639 works fine. Now, I need to have
OpenMPI set up on a production cluster, but openmpi-1.3XXX
Jeff Squyres wrote:
>
> If you do not have InfiniBand or iWARP hardware, you can disable this
> whole code path with:
> ./configure --without-openib ...
BINGO!
Both of my problems are gone with this configure flag and the
make ends successfully, also with the --enable-shared configure
flag.
On May 12, 2007, at 8:49 AM, Rob wrote:
> What version of OFED do you have installed, 1.0? We can probably add
> a proper configure test for IBV_EVENT_CLIENT_REREGISTER and
> protect those sections of the code for OFED installations that do
not have it.
OFED? Protect sections?
No idea what y
Jeff Squyres wrote:
>
> This stuff was just added the other day (remember: trunk = active
> ...
>
> What version of OFED do you have installed, 1.0? We can probably add
> a proper configure test for IBV_EVENT_CLIENT_REREGISTER and
> protect those sections of the code for OFED installations th
On May 12, 2007, at 8:25 AM, Rob wrote:
> This specific problem may be due to a bug that Brian just found/
fixed
> in the configure script last night (due to a bug report from Paul
Van
> Allsburg). Could you try any nightly trunk tarball after r14600 (the
> fix hasn't made its way over to the
Jeff Squyres wrote:
>
> This specific problem may be due to a bug that Brian just found/fixed
> in the configure script last night (due to a bug report from Paul Van
> Allsburg). Could you try any nightly trunk tarball after r14600 (the
> fix hasn't made its way over to the 1.2 release branch
Sorry for the delay in replying -- per the other thread, let's see if
the mpicc problem was fixed last night, and let's see the configure
output files to try to get an idea about what the problem was in
regards to the opal missing symbol.
To be honest, however, none of the current Open MPI
11 matches
Mail list logo
