M1 Rosetta build fails Python 3.9.10

I am using MacOS Monterey with M1 chip. I've opened a rosetta terminal by switching architectures using the following command:

```
$ arch -x86_64 /bin/zsh
```

Then, I try to install python:

```

$ asdf install python 3.9.10

python-build --patch 3.9.10 /Users/errc/.asdf/installs/python/3.9.10
with patch file from: https://github.com/python/cpython/commit/8ea6353.patch?full_index=1
python-build: use openssl@1.1 from homebrew
python-build: use readline from homebrew
Downloading Python-3.9.10.tar.xz...
-> https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tar.xz
Installing Python-3.9.10...
patching file Misc/NEWS.d/next/macOS/2020-06-24-13-51-57.bpo-41100.mcHdc5.rst
patching file configure
Hunk #1 FAILED at 3426.
1 out of 1 hunk FAILED -- saving rejects to file configure.rej
patching file configure.ac
Hunk #1 FAILED at 510.
1 out of 1 hunk FAILED -- saving rejects to file configure.ac.rej

BUILD FAILED (OS X 12.1 using python-build 2.2.4-1-1-g7ea04089)

Inspect or clean up the working tree at /var/folders/sz/pgt1clhs4sl3zw_qtl_3jjbh0000gn/T/python-build.20220202150238.51097
Results logged to /var/folders/sz/pgt1clhs4sl3zw_qtl_3jjbh0000gn/T/python-build.20220202150238.51097.log

Last 10 log lines:
/var/folders/sz/pgt1clhs4sl3zw_qtl_3jjbh0000gn/T/python-build.20220202150238.51097 /Users/Shared/v/asdf/arch
warning: xz not found; consider installing `xz` package
/var/folders/sz/pgt1clhs4sl3zw_qtl_3jjbh0000gn/T/python-build.20220202150238.51097/Python-3.9.10 /var/folders/sz/pgt1clhs4sl3zw_qtl_3jjbh0000gn/T/python-build.20220202150238.51097 /Users/Shared/v/asdf/arch

```

I even try with the patch:

```
$ export ASDF_PYTHON_PATCH_URL="https://github.com/python/cpython/commit/8ea6353.patch?full_index=1"
$ asdf install python 3.9.10

# Same error
```

Any idea why this is failing? Install/build works under the default arm64 architecture

Beginne damit, `asdf install python 3.9.10` in einem x86_64-Rosetta-Terminal nachzustellen, und prüfe die Ausgabe von `python-build` und das gespeicherte Build-Log. Vergleiche die Patch-URL sowie die abgelehnten Hunks von `configure` und `configure.ac` im temporären Build-Verzeichnis. Als erledigt gilt die Aufgabe, wenn die Ursache identifiziert ist und die Installation unter Rosetta erfolgreich ist oder die erforderliche Einschränkung und der Workaround dokumentiert sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.