Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Michael Stapelberg writes: > Could you provide the command line for doing this please? Sure, no problem. sudo apt install debootstrap debian-ports-archive-keyring sudo debootstrap --arch=x32 --variant=buildd \

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Could you provide the command line for doing this please? On Mon, Nov 13, 2017 at 5:20 PM, Aaron M. Ucko wrote: > Michael Stapelberg writes: > >> Do I understand correctly that you’re saying booting an amd64 machine >> with syscall.x32=y should suffice to

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Michael Stapelberg writes: > Do I understand correctly that you’re saying booting an amd64 machine > with syscall.x32=y should suffice to reproduce the issue? AIUI, that setting should let you work in a local x32 chroot, though you will of course have to set it up first

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Do I understand correctly that you’re saying booting an amd64 machine with syscall.x32=y should suffice to reproduce the issue? On Sun, Nov 12, 2017 at 6:17 PM, Aaron M. Ucko wrote: > Michael Stapelberg writes: > >> ucko, what’s the procedure here? How

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Michael Stapelberg writes: > ucko, what’s the procedure here? How can Steffen get access to a > machine on which to reproduce this issue? Good question. Technically, x32 is an alternate ABI for amd64, so the amd64 porter box could in principle additionally host x32

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Sorry, I just realized we don’t actually have an x32 porterbox listed at https://db.debian.org/machines.cgi. ucko, what’s the procedure here? How can Steffen get access to a machine on which to reproduce this issue? Thanks. On Fri, Nov 10, 2017 at 5:30 PM, Michael Stapelberg

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

You can get a guest account on Debian porter machines (we have one for each architecture which Debian supports). Please follow https://dsa.debian.org/doc/guest-account/, I’m happy to sponsor your request. On Fri, Nov 10, 2017 at 5:26 PM, Steffen Jaeckel wrote: > On 10/18/2017

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

On 10/18/2017 05:31 PM, Michael Stapelberg wrote: > [+cc steffen, karel] > > Any clues about this build failure? > > On Wed, Oct 18, 2017 at 8:22 AM, Aaron M. Ucko wrote: >> Source: libtomcrypt >> Version: 1.18-1 >> Severity: important >> Justification: fails to build from

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

[+cc steffen, karel] Any clues about this build failure? On Wed, Oct 18, 2017 at 8:22 AM, Aaron M. Ucko wrote: > Source: libtomcrypt > Version: 1.18-1 > Severity: important > Justification: fails to build from source (but built successfully in the past) > User:

Bug#879027: libtomcrypt: FTBFS on x32: final link failed: Bad value

Source: libtomcrypt Version: 1.18-1 Severity: important Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.or The latest build of libtomcrypt for x32 (admittedly not a release architecture) failed per the below excerpts from