From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#37850: Glib documentation is missing Date: Tue, 12 Nov 2019 19:34:58 +0100 Message-ID: <20191112183458.fmlullhdc65bp2am@pelzflorian.localdomain> References: <87v9sbj2ru.fsf@ambrevar.xyz> <87h83ret3a.fsf@ambrevar.xyz> <87k18gncbn.fsf@ambrevar.xyz> <8736f4ok77.fsf@devup.no> <87ftj4m0s0.fsf@ambrevar.xyz> <8736ewmyc1.fsf@devup.no> <87woc6kbhc.fsf@ambrevar.xyz> <20191112123233.jkcevtpkz5i2yut5@pelzflorian.localdomain> <20191112132254.hzqo2zck3btcerdb@pelzflorian.localdomain> <87h839gk47.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41081) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iUb1H-0001mp-VJ for bug-guix@gnu.org; Tue, 12 Nov 2019 13:36:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iUb1G-0003qM-U0 for bug-guix@gnu.org; Tue, 12 Nov 2019 13:36:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:49552) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iUb1G-0003q4-HG for bug-guix@gnu.org; Tue, 12 Nov 2019 13:36:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iUb1G-00072b-C1 for bug-guix@gnu.org; Tue, 12 Nov 2019 13:36:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87h839gk47.fsf@ambrevar.xyz> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Pierre Neidhardt Cc: 37850@debbugs.gnu.org On Tue, Nov 12, 2019 at 05:00:40PM +0100, Pierre Neidhardt wrote: > Hmmm, you are right, it does not get built during the install phase. > > I had a look at the bugtracker: > > https://gitlab.gnome.org/GNOME/glib/issues > > Could not find anything related to this. > > Could our Meson build system be buggy? > As a side note, it does not seem to print any command line flags, which > is a bit inconvenient for debugging. Something we could improve at least. > Moving a call to the “error” procedure in various places in the package and Guix’ meson-build-system.scm reveals (I think) that the package arguments are correctly rewritten by substitute-keyword-arguments, but the meson-build procedure from meson-build-system.scm is called with the original package’s args. Regards, Florian