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 926187 - myproxy: Does not support aarch64 in f19 and rawhide
Summary: myproxy: Does not support aarch64 in f19 and rawhide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: myproxy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
 
Reported: 2013-03-23 15:32 UTC by Dennis Gilmore
Modified: 2013-09-06 13:25 UTC (History)
4 users (show)

Fixed In Version: myproxy-5.9-6.fc20.armv7hl.rpm
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-06 13:25:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dennis Gilmore 2013-03-23 15:32:59 UTC 
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  myproxy 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/myproxy/myproxy-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.
Comment 1 Mattias Ellert 2013-03-24 07:05:11 UTC 
I have patched grid-packaging-tools to use --force-missing when automake is called.

In order to proceed further I need the following information:

1) What does the config.guess script return on this architecture?

2) What name is used for this architecture in %ifarch macros in spec files?

3) What does "uname -m" report on this architecture?

4) Does this architecture install libraries in /usr/lib or /usr/lib64?
Comment 2 Dennis Gilmore 2013-03-25 17:24:19 UTC 
libraries are installed into /usr/lib64 uname -m is aarch64 its also the rpm arch as to config.guess i cant get you that right now, we dont have any real hardware as it doesnt yet exist and are just getting things in place for the bringup. we are about to start building everything as rpms for the first time.
Comment 3 Mattias Ellert 2013-05-17 12:33:02 UTC 
Hi Dennis, one more question.

Does gcc and the rest of the tool chain on aarch64 support -m32/-m64 like on many other 64 bit architectures, or is it 64 bit only and using -m64 will break because it is an unsupported option?
Comment 4 Mattias Ellert 2013-07-29 04:54:54 UTC 
This should be fixable now by simply adding aarch64 to the list of 64 bit archs in the specfile:

--- a/myproxy.spec
+++ b/myproxy.spec
@@ -6,7 +6,7 @@
 %global with_sysv 0
 %endif
 
-%ifarch alpha ia64 ppc64 s390x sparc64 x86_64
+%ifarch aarch64 alpha ia64 ppc64 s390x sparc64 x86_64
 %global flavor gcc64
 %else
 %global flavor gcc32
Note You need to log in before you can comment on or make changes to this bug.