> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Steve Traylen
>
> On Mon, Nov 21, 2011 at 3:41 PM, David Crooks <[log in to unmask]>
> wrote:
> > Hi all,
> >
> > We've been having some problems at Glasgow updating our openmpi
> > installation having updated to torque 2.5.7 - to do this we need the
> > torque-devel-2.5.7 package, which we're having trouble finding an SL5
> > rpm for (I've checked with Steve Traylen, and it doesn't appear to be
> > in EPEL). Has anyone else had any similar problems - how do you handle
> > openmpi?
>
> Are you positive it's not the EPEL one? Which host was it built on , who
> signed it?
>
I think the problem is that they are running the EPEL torque,
but their OpenMPI build wants the torque development headers,
and has an RPM (build)requires on a named 'torque-devel' package,
and the EPEL one doesn't have it - it has 'libtorque-devel'.
I suspect simply hacking the OpenMPI stuff to look for that instead
would solve things.
Ewan
|