Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 924958
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. 389-ds-base 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 configure. 3. Apply the patch at http://ausil.fedorapeople.org/aarch64/389-ds-base/389-ds-base-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
When you work on this issue, could you please make the same change to 389-admin and 389-adminutil?
Thanks a lot!!
389-ds-base: Fix description: Reran autoconf (autoconf-2.69-3.fc18.noarch) on Fedora 18.
$ egrep aarch config. config.guess: aarch64:Linux::) config.guess: aarch64_be:Linux::) config.guess: UNAME_MACHINE=aarch64_be config.sub: | aarch64 | aarch64_be \ config.sub: | aarch64- | aarch64_be-* \
Pushed to master: commit 1a35074 Pushed to 389-ds-base-1.3.1: commit 856e3d2
389-adminutil: Fix description: Reran autoconf (autoconf-2.69-3.fc18.noarch) on Fedora 18.
Pushed to master: commit ebfca036ae1853e27255282c4a8033372e368b05
389-admin: This commit already applied autoconf 2.69. commit 6372efe532e5366e8d95c01fefbf4afceee0ac32 Author: Nathan Kinder nkinder@redhat.com Date: Tue Jun 19 14:16:05 2012 -0700 Ticket #329 - Port modules to httpd 2.4
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/680
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.