Bug 189441 – rebuild with tm support

Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 189441 - rebuild with tm support

Summary:	rebuild with tm support

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	openmpi (Show other bugs)
Sub Component:
Version:	16
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Doug Ledford
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-04-19 19:12 EDT by Garrick Staples
Modified:	2012-04-16 08:53 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-10-17 21:49:25 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Garrick Staples 2006-04-19 19:12:13 EDT

TORQUE is now in Extras.  Can openmpi be rebuilt with libtorque-devel to get tm
support?

Comment 1 Garrick Staples 2006-04-19 19:17:05 EDT

I forgot to mention, you need to change references to libpbs to libtorque in
openmpi's configure script until they patch it upstream.  You can just do 'sed
-i -e s/lpbs/ltorque/ configure', but here is a patch for 1.0.2 (I assume you
are updating soon.)
http://www-rcf.usc.edu/~garrick/openmpi-1.0.2-libtorque.patch

Comment 2 Sergio Belkin 2012-04-16 08:53:30 EDT

I don't know when, why or how, but the bug is still there, there is no support for torque:

ompi_info | grep tm

It has no output at all

When it should have :

  MCA ras: tm (MCA v2.0, API v2.0, Component v1.5.4)
  MCA plm: tm (MCA v2.0, API v2.0, Component v1.5.4)
  MCA ess: tm (MCA v2.0, API v2.0, Component v1.5.4)

Note You need to log in before you can comment on or make changes to this bug.