FEDORA-2016-46ffd0fe13

bugfix update in Fedora 23 for openblas and R

Status: testing 2 years ago

R now uses openblas instead of the unoptimized blas bundled with R (on all architectures where openblas is supported). In the previous update, this was done by symlinking /usr/lib64/R/lib/libRblas.so to /usr/lib64/libopenblas.so.0. While this worked fine for R, it did not work for anything linking to libR.so or trying to dynload libRblas.so.

To resolve this, a new openblas subpackage (openblas-Rblas) has been added, which contains a copy of openblas built as libRblas.so (and reporting libRblas.so as its soname). R now depends on openblas-Rblas on all architectures which support openblas and on all targets new enough to build openblas (RHEL 7+, Fedora 23+). Older targets or incompatible architectures use the unoptimized Rblas.

If you wish to switch from the openblas libRblas.so to the R provided blas, simply rename /usr/lib64/R/lib/libRrefblas.so to /usr/lib64/R/lib/libRblas.so.

Comments 3

This update has been submitted for testing by spot.

This update has been pushed to testing.

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes


Add Comment & Feedback
Toggle Preview

Comment fields support Fedora-Flavored Markdown. Comments are governed under this privacy policy.

-1 0 +1 Feedback Guidelines
#1392192 segfault during normal usage
#1404662 libR.so doesn't contain full path of libRblas.so
#1404796 libRblas.so()(64bit) is needed by package R-core-3.3.2-2.el5.x86_64
Is the update generally functional?
Content Type
RPM
Status
testing
Test Gating Status
Tests not running
Submitted by
Update Type
bugfix
Karma
0
stable threshold: 3
unstable threshold: -3
Autopush
Enabled
Dates
submitted 2 years ago
in testing 2 years ago

Related Bugs 3

00 #1392192 segfault during normal usage
00 #1404662 libR.so doesn't contain full path of libRblas.so
00 #1404796 libRblas.so()(64bit) is needed by package R-core-3.3.2-2.el5.x86_64

Automated Test Results

Test results and gating status may sometimes conflict as the gating status is retrieved periodically by Bodhi's backend server, while the test results presented here are retrieved upon page load. If your update is marked as gated while all the tests show green/passed, the next check of gating status should open the gate.