The newly introduced --enable-compressed-debug-section=all configure
flag in the base binutils package makes the mingw-w64 build system
unusable. For example:
$ guix build --target=x86_64-w64-mingw32 hello
and
$ guix build mingw-w64-x86_64-winpthreads
Will fail to build with an error:
"x86_64-w64-mingw32-ld: final link failed: bad value"
Turning off this flag seems to fix the problem, but perhaps it'd also be
worthwhile to investigate the root cause.
* gnu/packages/cross-base.scm (cross-binutils): When building for mingw
targets, append "--enable-compressed-debug-section=no" to configure
flags.
Add the CONFIG_SND_EMU10K1=m and CONFIG_SND_EMU10K1_SEQ=m kernel options to
all of our x86 and ARM configurations. The change automated via:
$ git grep -rl CONFIG_SND_INDIGODJX | xargs grep -rL CONFIG_SND_EMU10K1=m \
| xargs sed '/CONFIG_SND_INDIGODJX=m/a\
CONFIG_SND_EMU10K1=m\nCONFIG_SND_EMU10K1_SEQ=m' -i
ZONE_DMA is still used by some kernel drivers such as older sound and network
cards; it was already enabled on ARM and for some i686 kernels. Enable it
everywhere for consistency. The change was automated with:
$ git grep -rl CONFIG_ZONE_DMA | \
xargs sed 's/# CONFIG_ZONE_DMA is not set/CONFIG_ZONE_DMA=y/' -i
* gnu/packages/aux-files/linux-libre/4.14-x86_64.conf: Enable CONFIG_ZONE_DMA.
* gnu/packages/aux-files/linux-libre/4.19-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/4.4-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/4.9-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.10-i686.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.10-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.15-i686.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.15-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.16-i686.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.16-x86_64.conf: Likewise.
* gnu/packages/aux-files/linux-libre/5.4-x86_64.conf: Likewise.
Long ago we had a profile hook, called “texlive-configuration”, which would
operate on the texlive-* packages that have actually been installed in the
profile, build a union directory, and then install a texmf.cnf file that
declared the prefix of the TeX Live tree to be the union directory. It then
generated font maps based on the fonts that had actually been installed.
This approach had multiple disadvantages, the worst of which was that you
could only really have one TeX Live tree. Commit
04a0b1e09a addressed this, where texmf.cnf was
modified *once* and for all in texlive-bin to reference the GUIX_TEXMF
variable to determine the root of the tree. This made much of
“texlive-configuration” obsolete, because we didn’t need to have any union
directories at all, because we had no need for a customized per-profile
variant of texmf.cnf.
Unfortunately, with the loss of the profile hook we would no longer build font
maps. This patch resurrects the profile hook: we’re again generating font
maps (such as pdftex.map) based on the contents of the profile.
* gnu/packages/tex.scm (texlive-default-updmap.cfg): New variable.
* guix/profiles.scm (texlive-configuration): Rename this...
(texlive-font-maps): ...to this; update to run updmap-sys on the contents of
the profile to generate only font maps.
(%default-profile-hooks): Add texlive-font-maps.
* guix/status.scm (hook-message): Rename unused texlive-configuration to
texlive-font-maps.
* gnu/packages/audio.scm (webrtc-audio-processing)[arguments]: Adjust
custom arguments list to also fix building on all powerpc architectures.
[native-inputs]: Add patch, local-file on riscv64-linux and powerpc
architectures.
* gnu/packages/patches/webrtc-audio-processing-big-endian.patch: New file.
* gnu/local.mk (dist_patch_DATA): Add it.
This is a follow-up to 326e08bf0f, et.al.
* gnu/services/monitoring.scm (%zabbix-front-end-nginx-configuration): Rename
to ...
(%zabbix-front-end-configuration-nginx): ... this.
(zabbix-front-end-nginx-extension): Adjust accordingly.
...to make them in line with the newly generated front-end documentation.
* doc/guix.texi (Monitoring Services): Regenerate zabbix-server-configuration
and zabbix-agent-configuration.
Commit e301f1a8ed removed the NGINX argument
entirely, but users may rely on and override it. Reported by rekado on #guix.
* gnu/services/monitoring.scm (%zabbix-front-end-nginx-configuration): Restore
exported variable.
(zabbix-front-end-nginx-extension): New procedure.
(zabbix-front-end-configuration): Remove FASTCGI-PARAMS field. Restore NGINX
field, but default to the empty list.
(zabbix-front-end-service-type): Extend NGINX-SERVICE-TYPE by
ZABBIX-FRONT-END-NGINX-EXTENSION.
* doc/guix.texi (Monitoring Services): Regenerate documentation.
