From: "Ludovic Courtès" <ludo@gnu.org>
To: Roel Janssen <roel@gnu.org>
Cc: 48541@debbugs.gnu.org
Subject: [bug#48541] [PATCH] gnu: Fix build for ldc.
Date: Fri, 21 May 2021 16:57:01 +0200 [thread overview]
Message-ID: <87im3c6soy.fsf_-_@gnu.org> (raw)
In-Reply-To: <b7bb8636584d25befdb9a302d59e524f429f34bc.camel@gnu.org> (Roel Janssen's message of "Fri, 21 May 2021 12:24:00 +0200")
Hi!
Roel Janssen <roel@gnu.org> writes:
> I attached the test suite's logs for the failed tests. The complete log
> can be found in 'build/Testing/Temporary/LastTest.log' of the build
> directory of a failed build. It is too large to attach though.
>
> The log shows the following:
> ------
> Test runnable/b18504.d failed. The logged output:
> /tmp/guix-build-ldc-1.10.0.drv-0/build/bin/ldmd2 -conf= -m64 -Irunnable
> -g -g -link-defaultlib-debug -od../../../../build/dmd-testsuite-
> debug/runnable -of../../../../build/dmd-testsuite-
> debug/runnable/b18504_0 runnable/b18504.d
> gdb ../../../../build/dmd-testsuite-debug/runnable/b18504_0 --batch -x
> ../../../../build/dmd-testsuite-debug/runnable/b18504_0.gdb
> warning: Could not trace the inferior process.
> warning: ptrace: Operation not permitted
> ../../../../build/dmd-testsuite-debug/runnable/b18504_0.gdb:2: Error in
> sourced command file:
> During startup program exited with code 127.
>
> ------
Interesting. Looking at ptrace(2), it’s not supposed to fail with EPERM
in the build environment, unless again that’s because of the Yama thing
I mentioned. What’s the value of /proc/sys/kernel/yama/ptrace_scope on
your build machine?
So I’d say: adjust the comment with a link to
<https://issues.guix.gnu.org/48541>, saying that ptrace(2) fails with
EPERM, and push it.
We can always improve later if/when we find more info.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-05-21 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:08 [bug#48541] [PATCH] gnu: Fix build for ldc Roel Janssen
2021-05-21 10:09 ` Ludovic Courtès
2021-05-21 10:24 ` Roel Janssen
2021-05-21 14:57 ` Ludovic Courtès [this message]
2021-05-21 16:10 ` Roel Janssen
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=87im3c6soy.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=48541@debbugs.gnu.org \
--cc=roel@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.
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).