astral-sh / astral-sh/python-build-standalone
`PYTHON.json` inconsistent when building for armv7-unknown-linux-gnueabihf
- Lenguaje dominante
- Python
- Estrellas
- 4.4k
- Forks
- 316
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 27
Descripción
When building a python distribution for target armv7-unknown-linux-gnueabihf, the resulting file `PYTHON.json` contains several information indicating it was build for x86_64-unknown-linux-gnu.
### How to reproduce:
```
git clone https://github.com/indygreg/python-build-standalone.git
cd python-build-standalone
./build-linux.py --target armv7-unknown-linux-gnueabihf
```
The resulting `PYTHON.json` contains the following:
```json
{
"build_info": {
"core": {
"static_lib": "install/lib/python3.10/config-3.10-x86_64-linux-gnu/libpython3.10.a"
}
},
"python_config_vars": {
"BUILD_GNU_TYPE": "x86_64-unknown-linux-gnu",
"CONFIG_ARGS": "'--build=x86_64-unknown-linux-gnu' '--host=armv7-unknown-linux-gnueabihf' '--prefix=/install' '--with-openssl=/tools/deps' '--with-system-expat' '--with-system-libmpdec' '--without-ensurepip' '--with-readline=editline' '--enable-shared' '--with-dbmliborder=bdb' 'ac_cv_buggy_getaddrinfo=no' 'ac_cv_file__dev_ptc=no' 'ac_cv_file__dev_ptmx=no' 'build_alias=x86_64-unknown-linux-gnu' 'host_alias=armv7-unknown-linux-gnueabihf' 'CC=/usr/bin/arm-linux-gnueabihf-gcc' 'CFLAGS= -fPIC -I/tools/deps/include -I/tools/deps/include/ncursesw -I/tools/deps/libedit/include' 'LDFLAGS= -L/tools/deps/lib -Wl,--exclude-libs,ALL -L/tools/deps/libedit/lib' 'CPPFLAGS= -fPIC -I/tools/deps/include -I/tools/deps/include/ncursesw -I/tools/deps/libedit/include'",
},
}
```
I don't know whether this is a purely cosmetical or an actual issue, but it might be related to [this question](https://github.com/indygreg/PyOxidizer/discussions/696).
Guía de contribución
Línea de trabajo
Ejecuta ./build-linux.py --target armv7-unknown-linux-gnueabihf e inspecciona el PYTHON.json generado, especialmente build_info.core.static_lib y python_config_vars. Determina si los valores de x86_64 son meramente cosméticos o incorrectos para la compilación de armv7; se considera terminado cuando los metadatos describen de forma coherente el destino o el problema queda documentado como inofensivo.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- build-system
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100