From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35519@debbugs.gnu.org
Subject: bug#35519: librsvg broken on i686-linux
Date: Sat, 11 May 2019 04:03:41 -0400 [thread overview]
Message-ID: <878svd1kp3.fsf@netris.org> (raw)
In-Reply-To: <20190511020026.4d207749@scratchpost.org> (Danny Milosavljevic's message of "Sat, 11 May 2019 02:00:26 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> writes:
> But when I use our separate package definitions it fails when building libcore
> (which is the first library for the target compiler).
> Invoke seems to swallow the output, so I have no idea where or why it failed
> (grr).
Hmm. What makes you think that 'invoke' swallowed the output? You
might be right, but 'invoke' is used quite widely by now in Guix,
including to invoke 'make' in gnu-build-system, and I haven't seen
reports of it swallowing output.
I looked at the code. 'invoke' calls 'system*' which calls
'scm_open_process' (in libguile/posix.c) with an empty mode string.
In this case, the child STDOUT becomes (current-output-port) from the
parent if (current-output-port) is a "file port", i.e. a Guile port
backed by a POSIX file descriptor, e.g. a file, socket or pipe. If it's
a Guile port that's not backed by a file descriptor, e.g. a custom port,
soft port, string port, bytevector port, etc, then indeed the child
output will go to /dev/null instead.
(Note that the port returned by 'open-pipe*' when used in OPEN_BOTH mode
is also a soft port and not considered a file port, even though it is
internally backed by two file ports.)
Ditto for STDERR, except that it uses (current-error-port).
So, if 'invoke' seems to be swallowing output, it's probably because it
was called within the dynamic extent of 'with-output-to-port',
'with-error-to-port', 'with-output-to-string', or similar.
Regards,
Mark
next prev parent reply other threads:[~2019-05-11 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 3:43 bug#35519: librsvg broken on i686-linux Mark H Weaver
2019-05-10 12:53 ` Ricardo Wurmus
2019-05-11 0:00 ` Danny Milosavljevic
2019-05-11 8:03 ` Mark H Weaver [this message]
2019-05-11 14:16 ` Danny Milosavljevic
2019-05-11 14:08 ` Danny Milosavljevic
2019-09-16 12:24 ` Ludovic Courtès
2019-09-16 16:11 ` Danny Milosavljevic
2019-09-16 20:48 ` Ludovic Courtès
2020-03-18 20:45 ` bug#35519: guix master 4de63cf3fc0a831d75cb507456821104f24800c2: rust 1.19.0 build failure " Danny Milosavljevic
2020-12-18 15:19 ` Mathieu Othacehe
2020-12-20 13:22 ` Danny Milosavljevic
2021-10-19 21:44 ` bug#35519: Rust (and librsvg, IceCat, etc.) fails to build " scottworley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878svd1kp3.fsf@netris.org \
--to=mhw@netris.org \
--cc=35519@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).