Description of problem:
It seems that the TR1 component (at least) of the booth-math library isn't shipped. This seems to have been fixed in Fedora BZ#771370 but not backported to RHEL6.
Version-Release number of selected component (if applicable):
The SRPM here:
has a backport of the patch from Fedora commit 54ddcfc4141588bfa65356a1cd97aa2ecd8c3cdf which enables building of TR1, and also includes your patch for BZ #801534. I have it building overnight in mock presently.
Prospects for pushing an update?
This would be easy to backport and should be straightforward to test. TR1 libraries are part of boost and it is an omission not to ship them. People including headers from boost sub-tree (#include <boost/tr1/memory.hpp>) would notice this, otherwise (#include <memory>) I believe our core system is sufficiently complete to support TR1 even without boost.
OK - I can confirm that the backported patch added to the RPM above does resolve this problem (as well as 801534).
Thanks for your response. But I can't work out from your response whether you're saying a bug fix package will be pushed to rhel or not?
I am in the process of packaging up the FEniCS tools for EPEL and Fedora, and without these two fixes we won't be able to include it in EPEL.
(In reply to comment #4)
> Thanks for your response. But I can't work out from your response whether
> you're saying a bug fix package will be pushed to rhel or not?
It was a statement that the engineering part is not a problem. But there are more players in the process, and resource allocation compromises may prevent us from shipping this.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Chances of this being included as an update for 6.3, or as part of 6.4?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.