On 24 Feb 2018, at 15:29, Henrique de Moraes Holschuh <h...@debian.org> wrote: > On Sat, 24 Feb 2018, James Clarke wrote: >> Hi, >> Until today, config.guess (both upstream and in Debian) has lacked >> support for detecting x32, instead just printing out the tuple for >> amd64, x86_64-*-linux-gnu, and somehow this has gone unnoticed and not >> caused much issue (with one exception being llvm-toolchain-*, which ends >> up building a compiler which has amd64 as its default target). The above >> commit has just been applied upstream to detect an x32 system; please >> consider updating to the latest upstream version to include this change, >> or backport the single commit. > > Will do, expect the upload to unstable later today or tomorrow,
Great, thanks! > and if > you want me to, I can backport it to stretch-backports once it makes it > to testing in 10 days or thereabouts. > > However, if you need a stable *update* (not just a stable backport), I > will need a much stronger explanation to get the stable release manager > to approve it... Given x32 is in debian-ports and thus only has unstable/experimental, having it backported or included in a stable update is unnecessary, IMO. Of course, there may be other upstream changes you deem important, but unstable is enough for x32. Thanks, James
