systemd FTBFS on arm64

Bug #1746765 reported by Julian Andres Klode on 2018-02-01
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
binutils
Confirmed
Medium
binutils (Ubuntu)
Status tracked in Bionic
Bionic
Undecided
Unassigned
gnu-efi (Ubuntu)
Status tracked in Bionic
Bionic
Undecided
Julian Andres Klode
systemd (Ubuntu)
Status tracked in Bionic
Bionic
Undecided
Dimitri John Ledkov

Bug Description

Might be a bug in the toolchain, gnu-efi or systemd.

Changed in gnu-efi (Ubuntu):
assignee: nobody → Julian Andres Klode (juliank)
Changed in binutils:
importance: Unknown → Medium
status: Unknown → Confirmed
Julian Andres Klode (juliank) wrote :

It also FTBFS with the current gnu-efi, so my suggestion is to just disable the EFI integration on arm64.

Changed in gnu-efi (Ubuntu Bionic):
status: New → Invalid
Changed in systemd (Ubuntu Bionic):
status: New → Confirmed
Julian Andres Klode (juliank) wrote :

At least for now, so we don't block stuff.

Changed in gnu-efi (Ubuntu Bionic):
status: Invalid → New
Dimitri John Ledkov (xnox) wrote :

With new gnu-efi, the invalid relocation appears to be in side the gnu-efi crt object code. It seems to me that possibly fixes in either toolchain or gnu-efi, may resolve systemd build failure.

disabling gnu-efi feature of the systemd arm64 build.

Changed in systemd (Ubuntu Bionic):
status: Confirmed → In Progress
assignee: nobody → Dimitri John Ledkov (xnox)
Matthias Klose (doko) wrote :

this is now fixed in binutils

Changed in binutils (Ubuntu Bionic):
status: New → Fix Released
Changed in gnu-efi (Ubuntu Bionic):
status: New → Invalid
tags: added: id-5a7343dfc1d004a46568d4eb
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.