On 2016-07-25 18:08 +0100, Wookey wrote:
> On 2016-07-25 17:49 +0200, Sven Joachim wrote:
>> Source: jed
>> Version: 1:0.99.19-5
>> Severity: serious
>> Tags: patch
>>
>> The latest version of jed FTBFS on arm64[1] because config.sub is too
>> old:
>>
>> ,----
>> | checking build system type... Invalid configuration `aarch64-linux-gnu':
>> machine `aarch64' not recognized
>> | configure: error: /bin/bash autoconf/config.sub aarch64-linux-gnu failed
>> `----
>>
>> This should be fixed by replacing config.{sub,guess} with the files from
>> autotools-dev at build time. I have attached a possible patch which
>> does that via dh_update_autotools_config (included in debhelper since
>> version 9.20160114), but since I don't have an arm64 system, it's not
>> really tested.
>
> Doh!. I carefully updated to use dh_autoreconf to avoid exactly this
> sort of issue, but it's true that I only tested on x86.
>
> I do have an arm64 system now (as of last week!), and it's easy to
> test on the porter boxes too.
>
> When did "dh_update_autotools_config" appear?
In debhelper 9.20160114, my patch bumped the build dependency
accordingly.
> I've always used
> dh_autotools-dev_updateconfig
> and
> dh_autotools-dev_restoreconfig
> or is that what you meant?
> When might one use one or the other?
I don't really know, I guess dh_autotools-dev_{update,restore}config
might be a little bit friendlier to backporters, but there's also a
newer debhelper in backports. Essentially they do the same thing as
dh_update_autotools_config, though.
Cheers,
Sven
