Update scripts/config.{guess,sub} from autoconf v2.72

[robert-scheck]

Add support for riscv64 by updating scripts/config.{guess,sub} from autoconf v2.72, which currently fails with:

checking build system type... ./config.guess: unable to guess system type

References:

• https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=6199cff2909e0ac84c9391aa49ed097d6a33268d
• https://git.savannah.gnu.org/cgit/autoconf.git/plain/build-aux/config.guess?id=6199cff2909e0ac84c9391aa49ed097d6a33268d
• https://git.savannah.gnu.org/cgit/autoconf.git/plain/build-aux/config.sub?id=6199cff2909e0ac84c9391aa49ed097d6a33268d

Full build failure:

[…]
checking build system type... ./config.guess: unable to guess system type

This script, last modified 2015-12-14, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2015-12-14

uname -m = riscv64
uname -r = 6.5.0-1021-azure
uname -s = Linux
uname -v = #22~22.04.1-Ubuntu SMP Tue Apr 30 16:08:18 UTC 2024

/usr/bin/uname -p = 
/bin/uname -X     = 

hostinfo               = 
/bin/universe          = 
/usr/bin/arch -k       = 
/bin/arch              = riscv64
/usr/bin/oslevel       = 
/usr/convex/getsysinfo = 

UNAME_MACHINE = riscv64
UNAME_RELEASE = 6.5.0-1021-azure
UNAME_SYSTEM  = Linux
UNAME_VERSION = #22~22.04.1-Ubuntu SMP Tue Apr 30 16:08:18 UTC 2024
configure: error: cannot guess build type; you must specify one
[…]

[botovq]

Sorry for the delay - I was hoping to see the autoconf 2.72 update (finally) land in OpenBSD and test with that, but that didn't yet happen...

The files you suggest to merge don't match what was shipped in the 2.72 tarballs, but I don't think it matters a lot. I have checked that they match what's in the git repo. The diff is the usual unreviewable autoconf noise randomly adding and removing quotes to lines and using relative or full paths for other things.

As far as I'm concerned this can be merged (or I'll do it sometime next week unless there are objectons).

[cjeker]

On Fri, Jun 07, 2024 at 07:03:13AM -0700, Theo Buehler wrote: Sorry for the delay - I was hoping to see the autoconf 2.72 update (finally) land in OpenBSD and test with that, but that didn't yet happen...

Same here.

The files you suggest to merge don't match what was shipped in the 2.72 tarballs, but I don't think it matters a lot. I have checked that they match what's in the git repo. The diff is the usual unreviewable autoconf noise randomly adding and removing quotes to lines and using relative or full paths for other things. As far as I'm concerned this can be merged (or I'll do it sometime next week unless there are objectons).

Go ahead.

…

-- :wq Claudio

[robert-scheck]

The files you suggest to merge don't match what was shipped in the 2.72 tarballs […]

Oh dear…it seems it was too much expectation that the commit from the v2.72 tag matches the upstream release tarball.