This came up in #96008.
Without this patch modinfo always prints the module name for builtin
modules, even if an explicit --field is passed.

The default `strip` invocation tries to strip global symbols from the
library, and refuses because those are indirect symbol table
references.

The latter doesn't exist on Darwin (and, presumably, other targets as
well). This change allows emacsGcc from emacs-overlay to attempt to
build where previously, the derivation would error out.

Turns out that libgccjit gets installed as a .so file, which the gcc
builder.sh didn't change: It only touched .dylib files; that means
that anything linking in libgccjit.so would receive an "Image not
found" error at load time.

With this change, we invoke `install_name_tool` on .so files too,
adjusting their dynamic linker ID, so that they too can be found.

While at it, clean the derivation up a little.

glib: 2.64.4 -> 2.64.5

kbounce: init 20.04.3

patchelf: 0.11 -> 0.12

kigo: fix meta

kmod: add patch to correct behaviour with --field

mpg123: 1.26.2 -> 1.26.3

This reverts commit 96d6587.
The fix has been upstreamed a long time ago.

Backwards incompatible changes:
- Removed support for idna based U-label parsing in various X.509
  classes. This support was originally deprecated in version 2.1 and
  moved to an extra in 2.5.

This reverts commit edf2541.

Turns out lot of software (including Chromium) use bundled fontconfig
so we either need to wrap every one of those, or re-introduce the global
unversioned config. The latter is easier but weakens hermetic configs.

But perhaps those are not really worth the effort. Given that programs
linked against fc 2.12.6 on fc 2.13.92 system seem to at least display text,
even while printing tons of errors (as long as you generate fc cache manually),
and same thing the other way around, hopefully it will not be an issue in the future.

We give up on the hermetic configs in exchange for getting rid of lot of complexity.

The incompatibility does not seem to exist any more: programs linked against fc 2.12
on fc 2.14 system seem to at least display text, even while printing tons of errors
(as long as you generate fc cache manually), and same thing the other way around.
Hopefully it will not be an issue in the future.