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 926253 - nurbs++: Does not support aarch64 in f19 and rawhide
Summary: nurbs++: Does not support aarch64 in f19 and rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: nurbs++
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: mycae
QA Contact: Fedora Extras Quality Assurance
Depends On: 914222
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
Reported: 2013-03-23 15:37 UTC by Dennis Gilmore
Modified: 2013-07-05 16:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-07-05 16:32:22 UTC
Type: ---

Attachments (Terms of Use)

Description Dennis Gilmore 2013-03-23 15:37:37 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  nurbs++ 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 mycae 2013-07-05 16:32:22 UTC
Closing. As stated on other bug 924960, submitter did not respond to request on how to test. I do not have access to this architecture, so cannot fix.

Comment 2 Sergio Basto 2013-07-05 16:40:16 UTC
I don't if you read this so I post it here : 

as pointed out in this thread : 

The better solution is:   
  * Added: BuildRequires: autoconf, automake, libtool, pkgconfig
  * In "%prep" added: autoreconf --install --force 
( from )

anyway I also can't test it if works because I still don't have a koji for aarch64

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