bug#31974: If a phase returns #f, a warning is issued, but the build continues

2018-06-25 Thread Mark H Weaver
I just noticed that I made a mistake in commit d8a3b1b9e847d4a44d2695f95af77170d4d2788f, which changed 'gnu-build' in (guix build gnu-build-system) to issue a warning if a phase returns a value other than #t. The result is that if a phase returns a value other than #t, a warning is issued, but the

bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc

2018-06-25 Thread Marius Bakke
Mark H Weaver writes: > 'meson-build-system' includes 'patchelf' as an implicit input for all > packages that use it, and uses it from its 'fix-runpath' phase, > sometimes directly and sometimes via (guix build rpath). > > 'patchelf' is a nasty hack which seems to only work on Intel-based > syste

bug#31971: meson-build-system uses 'patchelf' which fails on armhf-linux etc

2018-06-25 Thread Mark H Weaver
'meson-build-system' includes 'patchelf' as an implicit input for all packages that use it, and uses it from its 'fix-runpath' phase, sometimes directly and sometimes via (guix build rpath). 'patchelf' is a nasty hack which seems to only work on Intel-based systems. It certainly doesn't work on '

bug#31970: epiphany: Strange "XXXXXXXXXXXXX..." entries in library RPATHs

2018-06-25 Thread Mark H Weaver
Since the upgrade from epiphany-3.24.4 to 3.28.1 in commit fc5c5b92cf7a1f6d65079f3840df502edcf58f50, https://git.savannah.gnu.org/cgit/guix.git/commit/?id=fc5c5b92cf7a1f6d65079f3840df502edcf58f50 which also changed the build-system from 'glib-or-gtk-build-system' to 'meson-build-system', warni

bug#31591: [bug#31934] [PATCH] services: sound: Properly handle alsa-plugins.

2018-06-25 Thread 宋文武
Oleg Pykhalov writes: > Hello, > > iyzs...@member.fsf.org (宋文武) writes: > >> Julien Lepiller writes: > > […] > >> Hello, after some hours of searching... I found that we can use the >> 'lib' option in 'pcm_type' and 'ctl_type' to specify the library path >> for alsa plugins, e.g: > > Thats a ni

bug#31961: java-libsnappy and java-libsnappy-1 have test failures (java.lang.UnsatisfiedLinkError)

2018-06-25 Thread Ricardo Wurmus
Björn Höfling writes: > java.lang.UnsatisfiedLinkError: /tmp/snappy-unknown-libsnappyjava.so: > /gnu/store/4ixlfq2baw24ihqx3058vcbq5sq9q5y3-gcc-4.9.4-lib/lib/libstdc++.so.6: > version `GLIBCXX_3.4.21' not found (required by > /gnu/store/4amdzkqix0grksrgw3h5wcv2azvz6pkd-snappy-1.1.7/lib/libsn

bug#31961: java-libsnappy and java-libsnappy-1 have test failures (java.lang.UnsatisfiedLinkError)

2018-06-25 Thread Björn Höfling
On Mon, 25 Jun 2018 12:11:18 +0200 Ricardo Wurmus wrote: > Björn Höfling writes: > > > java.lang.UnsatisfiedLinkError: /tmp/snappy-unknown-libsnappyjava.so: > > /gnu/store/4ixlfq2baw24ihqx3058vcbq5sq9q5y3-gcc-4.9.4-lib/lib/libstdc++.so.6: > > version `GLIBCXX_3.4.21' not found (required > > by

bug#31943: Some Maven bugs

2018-06-25 Thread Björn Höfling
On Sat, 23 Jun 2018 12:20:33 +0200 Julien Lepiller wrote: > Le Sat, 23 Jun 2018 00:39:35 +0200, > Björn Höfling a écrit : > > > 1) The following propagated inputs are used from bash scripts > > and are missing: which, coreutils > > > > 2) There is something wrong with the version output: >