Geoffroy,

It was not my intention to change anything. In fact I didn't noticed that. I 
just tried to use old spec file with newer version without success (I didn't 
try hard) and saw that provided spec file had all oscar %define, so I used it 
and didn't noticed the name space change.
Please ignore my mistakes or lack of understanding of all oscar architecture 
and make the appropriate choices.

My unique goal with openmpi 1.4.1 was to have a version that was more recent 
and that was able to handle infiniband. Nothing more. (redhat version lack that)
The only thing that may be of interest to check is the option to the configure 
script I put in the spec file. I can't remember if I did change or add some 
--with- switches (and I have no access to my devel platform right now).

Best regards.

Olivier.

Le lundi 3 mai 2010 04:52:28, vous avez écrit :
> Olivier,
> 
> Why did you change the namespace related to ompi (openmpi-oscar to openmpi). 
> Did you do that because you do not want to install the distro related version 
> of ompi? If so, it is exactly the opposite of the initial goal: allow users 
> to install both version.
> 
> Can you give me more details?
> 
> Thanks,
> 
> ----- "Olivier LAHAYE" <olivier.lah...@cea.fr> a écrit :
> 
> > Hi,
> > 
> > Here are svndiff against oscar-svn 9202 regarding opkg-openmpi.
> > this allows to upgrade to openmpi 1.4.1
> > 
> > The aim is to have an openmpi version greater than RHEL/CentOS/SL
> > openmpi package and avoid yum to install the distro version instead of
> > oscar version (that includes specific options)
> > 
> > Regards,
> > 
> > Olivier.
> 
> 

-- 
        Olivier LAHAYE
        CEAEA Saclay
        DRT-LIST-DCSI-DIR

------------------------------------------------------------------------------
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to