makedumpfile needs porting for AArch64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro AArch64 cross-distro work |
New
|
Undecided
|
Unassigned | ||
makedumpfile (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
dann frazier |
Bug Description
[Impact]
kdump-tools is not installable on arm64 because it depends on makedumpfile, which is not currently built on arm64. Adding arm64 to the Architecture list in debian/control is all that is needed for it to build successfully.
That said, xenial's version was too old to support filtering kdump-enabled xenial kernels (>= 4.10.0). So, this doesn't actually produce a *useful* makedumpfile, but does allow kdump-tools to be installed, which unblocks collection of (unfiltered) crash dump files.
[Test Case]
On an arm64 system:
sudo apt install kdump-tools
[Regression Risk]
The only change here is to make a binary package available on arm64 that previously was not - regression risk to existing architectures should therefore be negligible.
Note: Enabling a binary package for an architecture where it's known not to be useful - at last on it's own - is obviously non-ideal. I considered other options, but they all seem to add unnecessary regression risk:
- Demoting the "Depends:" to a "Recommends:". I actually think we should do this going forward (https:/
- Demoting only on arm64: This isn't possible unless we switch kdump-tools from Binary: any to Binary: all. I also think there are good reasons to do that in future releases (https:/
tags: | added: arm64 |
Changed in makedumpfile (Ubuntu): | |
status: | New → Confirmed |
tags: | added: ftbfs |
Changed in makedumpfile (Ubuntu Xenial): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
description: | updated |
As today's version 1.5.9-5ubuntu0.1, there is already arch/arm64.c available, but it's still not included in debian/control. It does build in my arm64 docker env, haven't tried yet.