"Soon". I wish that I could give a better answer than that, but not
being a professional software shop, we never commit to release dates.
The betas are getting more and more stable, though -- you might want to
try the latest 7.1.2 beta:
http://www.lam-mpi.org/beta/
On Mar 25, 2005, at 9:37 PM, Eric Swenson wrote:
> This bug affects us as well, so I was just wondering when LAM v7.1.2
> looks like it's going to be released..
>
> Thanks!
> Eric
>
>
> On Thu, 2005-03-24 at 12:07 -0500, Jeff Squyres wrote:
>> We had some more discussions about this off-list, and Ilya generously
>> got me a guest account on their cluster in order to replicate the
>> problem and investigate a fix. Etnus (the makers of Totalview)
>> confirmed that this is a debugging symbol bug in some versions of gcc,
>> and recommended a workaround (reordering the order of some #include
>> files so that struct definitions are not masked).
>>
>> This workaround is included in the upcoming v7.1.2 of LAM/MPI.
>>
>> Thanks to Ilya and Etnus for identifying and providing a workaround
>> for
>> this issue!
>>
>>
>>
>> On Mar 16, 2005, at 5:01 PM, Ilya Lashuk wrote:
>>
>>> Jeff Squyres wrote:
>>>
>>>> Please run "file liblam_totalview.so.0.0.0.0".
>>>
>>>
>>> Probably you meant file "liblam_totalview.so.0.0.0" - i don't have
>>> "file liblam_totalview.so.0.0.0.0". Here's the output:
>>> [ilashuk_at_master lam]$ file liblam_totalview.so.0.0.0
>>> liblam_totalview.so.0.0.0: ELF 32-bit LSB shared object, Intel 80386,
>>> version 1 (SYSV), not stripped
>>>
>>>> Just curious -- do you only have one MPI implementation installed on
>>>> your cluster (LAM/MPI 7.1.1)? If you have more than one, are you
>>>> sure that you have your PATH and LD_LIBRARY_PATH setup properly such
>>>> that they point to the 7.1.1 install?
>>>
>>> I also have mpich2 and mpich 1.2.6 installed. lam and mpich2 are
>>> installed in my home dir, mpich-1.2.6 is installed as root. I do not
>>> have "LD_LIBRARY_PATH" in my environment. "which" tells me that
>>> mpirun, mpicc, etc. come from lam.
>>>
>>>> What was the exact command line that you used to configure LAM/MPI?
>>>> (look in the first few lines of config.log in the LAM source
>>>> directory)
>>>
>>>
>>> ./configure FFLAGS=-O0 CFLAGS=-O0 CXXFLAGS=-O0
>>> --prefix=/home/guests/ilashuk/lam_install
>>>
>>> Turning off optimization was just a last resort (maybe without much
>>> sense) to make it work with hypre using "sysv" or "usysv" rpis.
>>> Totalview problems emerged as well when configured just with
>>> "./configure --prefix=/home/guests/ilashuk/lam_install", to my
>>> recollection.
>>>
>>> _______________________________________________
>>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>>
>>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
