Most of my failed packages, or a large chunck of them  die like this:

[626/639] env PKG_CONFIG_PATH=/var/tmp/portage/dev-libs/glib-2.84.0/work/glib-2.84.0-abi_x86_64.amd64/meson-uninstalled:/var/tmp/portage/dev-libs/glib-2.84.0/temp/python3.13/pkgconfig:/opt/cuda/pkgconfig:/usr/share/pkgconfig
PKG_CONFIG_LIBDIR=/usr/lib64/pkgconfig PKG_CONFIG=/usr/bin/x86_64-pc-linux-gnu-pkg->
FAILED: girepository/introspection/GLib-2.0.gir
env PKG_CONFIG_PATH=/var/tmp/portage/dev-libs/glib-2.84.0/work/glib-2.84.0-abi_x86_64.amd64/meson-uninstalled:/var/tmp/portage/dev-libs/glib-2.84.0/temp/python3.13/pkgconfig:/opt/cuda/pkgconfig:/usr/share/pkgconfig
PKG_CONFIG_LIBDIR=/usr/lib64/pkgconfig PKG_CONFIG=/usr/bin/x86_64-pc-linux-gnu-pkg-config CC=>
Traceback (most recent call last):
  File "/usr/bin/g-ir-scanner", line 104, in <module>
    sys.exit(scanner_main(sys.argv))
             ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/gobject-introspection/giscanner/scannermain.py",
line 601, in scanner_main
    ss, filenames = create_source_scanner(options, args)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/gobject-introspection/giscanner/scannermain.py",
line 468, in create_source_scanner
    ss.parse_files(filenames)
  File "/usr/lib64/gobject-introspection/giscanner/sourcescanner.py",
line 266, in parse_files
    self._parse(headers)
  File "/usr/lib64/gobject-introspection/giscanner/sourcescanner.py",
line 298, in _parse
    cc = CCompiler(compiler_name=self._compiler)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/gobject-introspection/giscanner/ccompiler.py", line
175, in __init__
    compiler_name = distutils.ccompiler.get_default_compiler()
                    ^^^^^^^^^^^^^^^^^^^
AttributeError: module 'distutils' has no attribute 'ccompiler'. Did you
mean: 'compilers'?
ninja: build stopped: subcommand failed.


Back in the good old days, everything was a header file in
/usr/include.  =(

Apparently "distutils" is some kind of compatibility package, I
**THINK** I found a version of it in each of the .../lib64/python directories... I have 0 understanding of how python finds its
dependencies. In ccompiler.py, it just says "import distutils" which is
like #include <distutils.h> which would mean I should look in /usr/include....   I think I'm trying to use Python 3.13.... The problem
is that when I look at distutils, I find it's a directory (!!!).   /usr/lib/python3.13/site-packages/setuptools/_distutils It has a
ccompiler.py that is extremely terse but does list
get_default_compiler.... I don't know what's up with that underscore, I
tried to import it as _distutils but that failed...

I'm looking at /usr/lib/python3.13/site-packages/setuptools/_distutils/compilers/C/base.py
and it looks fine.... So I have no idea why this is causing me so much
agony... =(

--
You can't out-crazy a Democrat.
WhY aRe ThEy KiLlInG tEh ChIcKeNs?
White is the new Kulak.
Powers are not rights.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------c3VakfxQhoru5R48RMnvg6ZK
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3/10/25 6:23 PM, Alan Grimes wrote:

Back in the good old days, everything was a header file in /usr/
include.  =(

Apparently "distutils" is some kind of compatibility package, I

Distutils is a build system, like autoconf or meson or cmake.

**THINK** I found a version of it in each of the .../lib64/python directories... I have 0 understanding of how python finds its
dependencies. In ccompiler.py, it just says "import distutils" which is
like #include <distutils.h> which would mean I should look in /usr/ include....   I think I'm trying to use Python 3.13.... The problem is
that when I look at distutils, I find it's a directory (!!!).   /usr/ lib/python3.13/site-packages/setuptools/_distutils It has a ccompiler.py
that is extremely terse but does list get_default_compiler.... I don't
know what's up with that underscore, I tried to import it as _distutils
but that failed...

I'm looking at /usr/lib/python3.13/site-packages/setuptools/_distutils/ compilers/C/base.py and it looks fine.... So I have no idea why this is causing me so much agony... =(

If you think that "import distutils" is anything like a C-equivalent
"#include <distutils.h>" then I think this is just a sign that your many
skills do NOT include a knowledge of Python.

The bug has been reported a bunch of times already. It's fixed, if you
emerge --sync.

See e.g. https://bugs.gentoo.org/951055

Note that the fix was to MASK a package version which was only available
in ~arch, you will need to downgrade that package.



--
Eli Schwartz

--------------c3VakfxQhoru5R48RMnvg6ZK--

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZ89pHQUDAAAAAAAKCRCEp9ErcA0vVxZ0 AQDxgOyXRQ/fqVHulcZ8SBS3aqTlkIjUNVZMSbGR/g6mlAEA0IBghO20BaT+XZZWwD3fkVePaxte OkdJEY18yY8eDAU=
=rNnT
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Mar 10, 2025 at 06:23:56PM -0400, Alan Grimes wrote:

Most of my failed packages, or a large chunck of them  die like this:

AttributeError: module 'distutils' has no attribute 'ccompiler'. Did you mean: 'compilers'?

emerge --sync and update, the latest setuptools was masked because of
that and it should make you downgrade it.

e.g. https://bugs.gentoo.org/950978
--
ionen

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmfPaAcACgkQskQGsLCs QzT7jQgAue8z6DsgZ3zXTpWAL+Y6qf4xkbr86WFX5dJZ0S1ycg85bN+5i8cXU16l Pmp1Tjr0KqtXeo6TL6qZ6m3lxpdwIKLpn6N0Bc8WsJA1plIjy5Trk5+OWq9rzpaO b4m58FtInpFlJa6JuRu7etGPWIjE39pd6bPQvld9peBd/D5BNT7f6L9BhSKFZQ88 yAP3m/SNNb9RcLEFPPSLXl5N7p8ooiDc4IschKXE4C76C5Q7++oLvT6BcZQW1qe2 DtZd0QI1Nj1/tG249+aq1uokdYfrO5SW5DuuqZfOqqKTSkgAvuP+KUSwKCqkeJgP XB7SPmcYMbTaCWJo9rNgdXjumDNikw==
=mwZF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)