Bug 1022970 - Does not build on AArch64
Does not build on AArch64
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: libdb (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jan Staněk
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-24 07:41 EDT by Marcin Juszkiewicz
Modified: 2013-11-06 04:55 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-06 04:55:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
fix for a bug (965 bytes, patch)
2013-10-24 07:41 EDT, Marcin Juszkiewicz
no flags Details | Diff

  None (edit)
Description Marcin Juszkiewicz 2013-10-24 07:41:18 EDT
Created attachment 815738 [details]
fix for a bug

Description of problem:

db-5.3.2x (x={1,8}) contains 4 copies of gnu-config files. All of them are too old to support AArch64 architecture. 

%configure macro takes care only of one copy (and fails) so we need to take of it on our own.

Version-Release number of selected component (if applicable):

5.3.21-11.fc19
5.3.28-1.fc21

How reproducible:

always

Steps to Reproduce:
1. rebuild it on aarch64
2.
3.

Actual results:

configure: creating cache config.cache
checking build system type... Invalid configuration `aarch64-redhat-linux-gnu': machine `aarch64-redhat' not recognized
configure: error: /bin/sh ../config.sub aarch64-redhat-linux-gnu failed

Expected results:

package builds

Additional info:
Comment 1 Jan Staněk 2013-11-06 04:48:57 EST
Packages built into rawhide with new config files. Marcin, please confirm that the package builds for you.
Comment 2 Marcin Juszkiewicz 2013-11-06 04:51:30 EST
We do not have rawhide for AArch64 yet. But we use same fix for our F19 based build.
Comment 3 Jan Staněk 2013-11-06 04:55:25 EST
That's fine for me, so I consider this bug fixed.

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