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 bugzilla.redhat.com.
Bug 925335
Summary: | ffcall: Does not support aarch64 in f19 and rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dennis Gilmore <dennis> |
Component: | ffcall | Assignee: | Jerry James <loganjerry> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | bruno, loganjerry, michel, pbrobinson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-20 14:02:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 922257 |
Description
Dennis Gilmore
2013-03-23 00:25:25 UTC
This package contains a bunch of assembly, in order to act as glue code from non-C languages to C libraries. Fixing this bug properly will require the writing of appropriate assembly language for the aarch64 platform. In the meantime, I have added an ExclusiveArch tag to the spec file to explicitly list the architectures that ffcall supports. (I believe that all current Fedora architectures are supported, and that aarch64 will be the first unsupported one.) I am not competent to write the necessary assembly. I am willing to approach upstream about adding aarch64 support, but will probably need to offer them both documentation and a way of testing their work. If somebody could help me acquire those two items, I will see if upstream is willing to do the work. Update: upstream is dead. The web site asks for a volunteer to be the new maintainer. This won't get fixed unless somebody well versed in aarch64 assembly is willing to do the work. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 I think we'll close this as won't fix. If it's dead upstream might be worth retiring it in general. Actually, there was some movement on a GSOC for ffcall last summer, although I haven't heard anything since. So there is still a chance that something will happen upstream someday. In any case, retiring ffcall would necessitate retiring clisp as well, which I'm not quite ready to do. There has been recent (i.e., last 2 weeks) activity there. I'm taking a "wait and see" stance for the moment. There has been some recent activity in the libffcall git indeed: http://git.savannah.gnu.org/gitweb/?p=libffcall.git;a=shortlog All I see are the commits from August 2015 which went into the 1.12 release, which is what we have in Fedora. Am I missing something? You need to look into the git repository at https://savannah.gnu.org/git/?group=libffcall . The previous CVS repository is dead. Cf. the announcement at http://lists.gnu.org/archive/html/libffcall/2016-12/msg00001.html |