From: Matt Wette <matt.wette@gmail.com>
To: 61788@debbugs.gnu.org
Subject: bug#61788: [3.0.9] --disable-tmpnam build fails "make check"
Date: Sat, 25 Feb 2023 10:24:25 -0800 [thread overview]
Message-ID: <02f61f79-448b-2c58-3a11-0127402fb06b@gmail.com> (raw)
I built gule-3.0.9 with "configure --disable-tmpnam" and get the
following failure from posix.test while running "make check":
Running ports.test
warning: call to primitive-fork while multiple threads are running;
further behavior unspecified. See "Processes" in the
manual, for more information.
Running posix.test
In execvp of something-that-does-not-exist: No such file or directory
In execvp of something-that-does-not-exist: No such file or directory
In execvp of something-that-does-not-exist: No such file or directory
ERROR: posix.test: system*: https://bugs.gnu.org/52835 - arguments:
((unbound-variable #f "Unbound variable: ~S" (tmpnam) #f))
Running print.test
I'm guessing this should use mkstemp instead, but I could not get
it to work.
reply other threads:[~2023-02-25 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02f61f79-448b-2c58-3a11-0127402fb06b@gmail.com \
--to=matt.wette@gmail.com \
--cc=61788@debbugs.gnu.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.
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).