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 926260 - ocaml: Does not support aarch64 in f19 and rawhide
Summary: ocaml: Does not support aarch64 in f19 and rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: ocaml
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
Reported: 2013-03-23 15:38 UTC by Dennis Gilmore
Modified: 2014-01-03 14:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-01-03 14:12:16 UTC
Type: ---

Attachments (Terms of Use)

Description Dennis Gilmore 2013-03-23 15:38:07 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  ocaml appears to use an earlier version of 
autoconf, preventing its being built.  This can be fixed in of three ways (In order of preference):

1. Work with upstream to migrate the package to autoconf 2.69.

2. Rerun autoconf or autoreconf in %prep or %build prior to running 

3. Apply the patch at
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Richard W.M. Jones 2013-03-25 08:31:51 UTC
Changing autoconf version is only about 0.1% of the problem
here.  We will need to write an AArch64 code generator too.  I
have asked upstream if anyone has looked into this, and they
are looking at it but prefer to wait until real hardware is

Comment 2 Richard W.M. Jones 2013-12-22 22:26:08 UTC
There is now an arm64 code gen for OCaml:

Comment 3 Richard W.M. Jones 2014-01-03 14:12:16 UTC
Earlier this week I backported the arm64 code gen to Rawhide.
This bug is fixed in ocaml-4.01.0-6.fc21.

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