Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 947477 - R-RScaLAPACK doesn't use platform CFLAGS causing FTBFS on ARM
Summary: R-RScaLAPACK doesn't use platform CFLAGS causing FTBFS on ARM
Alias: None
Product: Fedora
Classification: Fedora
Component: R-RScaLAPACK
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2013-04-02 14:15 UTC by Peter Robinson
Modified: 2013-12-11 22:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-12-11 22:21:56 UTC
Type: Bug

Attachments (Terms of Use)

Description Peter Robinson 2013-04-02 14:15:38 UTC
ARM doesn't support the -m32/-m64 and as a result is FTBFS which indicates that R-RScaLAPACK isn't using the ditro specific compiler flags.

Comment 1 Tom "spot" Callaway 2013-04-02 15:07:59 UTC
I don't know how that -m64 popped into the linker command string. You can see in the logs that the R-RScaLAPACK.spec is not passing it in anywhere.

The value for MPISHLIB_LD is evaluated from R_SHLIB_LD, which is R CMD config SHLIB_LD. You can see in the build log that R_SHLIB_LD does not include -m64, and that MPISHLIB_LD doesn't either.

The only place -m64 ever appears in the build logs is at that single linker invocation. I have no idea how to resolve this. If you had a prepped tree on the arm target, you might be able to grep it for the "-m64" string and see where it ends up getting added... that might shed some light on this.

Comment 2 Fedora End Of Life 2013-09-16 13:25:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:

Comment 3 Peter Robinson 2013-12-11 22:21:56 UTC
Package is retired and dead upstream

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