error: command 'gcc' failed: No such file or directory

[matthieumarrast]

Our continuous integration pipeline suddenly failed with error (pacakge "psycopg-c" source code compilation), after switching to the new docker image.

Previous image used: metwork/mfdataplugins-centos8-buildimage:release_2.2
New image used: metwork/mfdata-rocky8:2.2.4

It seems gcc is not present anymore in the new image.

Building wheels for collected packages: psycopg-c
  Building wheel for psycopg-c (pyproject.toml): started
  Building wheel for psycopg-c (pyproject.toml): finished with status 'error'
  error: subprocess-exited-with-error
  
  × Building wheel for psycopg-c (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [36 lines of output]
      /builds/aeroweb/data/mfdata_aeroweb_image_importer/python3_virtualenv_sources/tempolayer1159/tmp/pip-build-env-omdzco0z/overlay/lib/python3.11/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
      !!
      
              ********************************************************************************
              Please consider removing the following classifiers in favor of a SPDX license expression:
      
              License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3)
      
              See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
              ********************************************************************************
      
      !!
        self._finalize_license_expression()
      running bdist_wheel
      running build
      running build_py
      creating build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/__init__.py -> build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/_uuid.py -> build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/version.py -> build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/_psycopg.pyi -> build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/py.typed -> build/lib.linux-x86_64-cpython-311/psycopg_c
      copying psycopg_c/pq.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c
      creating build/lib.linux-x86_64-cpython-311/psycopg_c/_psycopg
      copying psycopg_c/_psycopg/__init__.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c/_psycopg
      copying psycopg_c/_psycopg/endian.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c/_psycopg
      copying psycopg_c/_psycopg/oids.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c/_psycopg
      creating build/lib.linux-x86_64-cpython-311/psycopg_c/pq
      copying psycopg_c/pq/__init__.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c/pq
      copying psycopg_c/pq/libpq.pxd -> build/lib.linux-x86_64-cpython-311/psycopg_c/pq
      running build_ext
      building 'psycopg_c._psycopg' extension
      creating build/temp.linux-x86_64-cpython-311/psycopg_c
      creating build/temp.linux-x86_64-cpython-311/psycopg_c/types
      gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/opt/metwork-mfext-2.2/opt/python3_core/../core/include -fPIC -I/opt/metwork-mfext-2.2/opt/scientific_core/include -I/opt/metwork-mfext-2.2/opt/python3_core/include/python3.11 -c psycopg_c/_psycopg.c -o build/temp.linux-x86_64-cpython-311/psycopg_c/_psycopg.o
      error: command 'gcc' failed: No such file or directory
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for psycopg-c
Failed to build psycopg-c
ERROR: Could not build wheels for psycopg-c, which is required to install pyproject.toml-based projects
ERROR with freeze_requirements
make: *** [/opt/metwork-mfext-2.2/share/plugin.mk:60: python3_virtualenv_sources/requirements3.txt] Error 1

[thebaptiste]

The new images no longer inherit from the "development" images of the Metwork CI. They are just "bare" rocky images with mdata, mfserv or mfbase installed. They do not have gcc or any devel rpms or any development tool installed.
So please add gcc in your CI.

[matthieumarrast]

For us compiling sources of python packages is a metwork functionnality.
gcc is used automatically by metwork. It's not our decision to use gcc for packages not available as binary (wheel).

[thebaptiste]

It's not a Metwork functionality, it's the functionment of pip... When you will build python packages not available as wheels and requiring devels rpm, you will also ask them to be added in Metwork images ?

I will add gcc in next images (with new tags) but I will not create new releases of mfbase, mfdata or mfserv 2.2 (or 2.1 or 2.3) just for that (so may be there will never be an image metwork/mfdata-rocky8:2.2.5 with gcc...).
If you wan't I can rebuild metwork/mfdata-rocky8:2.2.4 (but it will be the same image tag).

It's not forbidden to resolve such tiny details in your CI !