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 926718 - whatsup: Does not support aarch64 in f19 and rawhide
Summary: whatsup: Does not support aarch64 in f19 and rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: whatsup
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: David Brown
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
Reported: 2013-03-23 16:31 UTC by Dennis Gilmore
Modified: 2013-05-14 18:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-05-14 18:14:11 UTC
Type: ---

Attachments (Terms of Use)

Description Dennis Gilmore 2013-03-23 16:31:30 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  whatsup 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 David Brown 2013-03-24 06:04:03 UTC
I'm fine with trying to do an or autoreconf like thing in the spec file. May have to ask upstream for more build info to regenerate this. However, I've been trying to find a place to test the aarch64 to make sure it works. So far I've got the simulator from the arm website got the latest img-foundation.axf from linaro and am using the latest rootfs.git from but there's so many missing pieces to the image, yum doesn't work because its missing libffi. There isn't even an sshd or clients for ssh. 

I guess I don't see the progress yet to really get this fixed right now, since I'm having to build all the dependencies for this package to even check to see if it works.

So am I missing something or is the above where aarch64 is at right now?

Comment 2 David Brown 2013-03-24 16:31:31 UTC
Okay, is it better to do an autoreconf in the spec file or call %{GNUconfigure} ??

Comment 3 David Brown 2013-03-24 19:27:09 UTC
Oh, GNUconfigure doesn't work...

So, autoreconf doesn't work so well with these packages. I'll talk to upstream about getting that part fixed but I'm kind of confused. The config.guess and config.sub are part of automake not autoconf. So why does upstream need to support autoconf 2.69 when the config.sub/config.guess from older automakes won't have the aarch64 in it?

Comment 4 David Brown 2013-03-24 23:56:57 UTC
for future reference I'll need to test this but I think

autoreconf -I config -f -i

should work for both genders and whatsup.

Comment 5 David Brown 2013-05-06 16:22:10 UTC
I have versions of both genders and whatsup that should fix this issue but every time I remember I need to run fedpkg update we're in some sort of f19 freeze.

Here's the koji builds for both just in case you want to test things out.

Comment 6 David Brown 2013-05-14 18:14:11 UTC
This should be resolved now, the update automagically got pushed for me.

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