--- Begin Message ---
Subject: |
32-bit to 64-bit cross-builds |
Date: |
Wed, 8 Mar 2017 11:46:03 +0200 |
User-agent: |
Mutt/1.8.0 (2017-02-23) |
Currently in build-aux/hydra we have i686->x86_64 cross-builds disabled,
but this is not the only one we should eliminate. Currently on
core-updates we have armhf->mips64el attempts and also armhf and i686->
aarch64 attemps, all of which fail as expected.
I propose we add two sub-lists of %supported-architectures, 32-bit and
64-bit; we can use them in package difinitions to eliminate 32-bit
architectures from building 64-bit only packages, and use them in
build-aux/hydra to prevent 32-bit -> 64-bit cross-builds.
--
Efraim Flashner <address@hidden> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#26022: 32-bit to 64-bit cross-builds |
Date: |
Thu, 09 Mar 2017 16:29:53 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Efraim Flashner <address@hidden> skribis:
> Currently in build-aux/hydra we have i686->x86_64 cross-builds disabled,
> but this is not the only one we should eliminate. Currently on
> core-updates we have armhf->mips64el attempts and also armhf and i686->
> aarch64 attemps, all of which fail as expected.
>
> I propose we add two sub-lists of %supported-architectures, 32-bit and
> 64-bit; we can use them in package difinitions to eliminate 32-bit
> architectures from building 64-bit only packages, and use them in
> build-aux/hydra to prevent 32-bit -> 64-bit cross-builds.
I believe this if fixed in 9ec2a4d3fec44f08a55df9f5f3d1a04b83e7fcf6, not
by specifying a list of valid cross-builds, but by fixing the logic in
the ‘from-32-to-64?’ procedure.
Thanks,
Ludo’.
--- End Message ---