unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Carl Dong <contact@carldong.me>
To: 50203@debbugs.gnu.org
Subject: bug#50203: binutils-mesboot0: configure: sed: command not found
Date: Wed, 25 Aug 2021 15:17:26 -0400	[thread overview]
Message-ID: <1FF8D553-4B61-400A-AD0B-6A9A0CCFDEA8@carldong.me> (raw)

Hi all,

After resolving bug#49985, a new build failure has stumped a community member of mine. When building /gnu/store/8kap9kj0ayhaqd4ay7n9lgpbcwankxrq-binutils-mesboot0-2.14.drv, the build fails and the logs are as follows: https://paste.sr.ht/~dongcarl/7fe559b338dfa9aa3cf3464dbdab8109487c9783#8kap9kj0ayhaqd4ay7n9lgpbcwankxrq-binutils-mesboot0-2.14.log-L5504

We’ve tried the normal suspects: --cores=1, reboots, mounting tmpfs at /tmp, etc.

What’s also fascinating is that, when I inspect his keep-failed directory: https://nextcloud.carl.homeserver.net/s/ZHmAbz3LwyPwcfL
We found that:

1. The $PATH in the environment-variables file contained /gnu/store/2z4y0n547x7d566281isklk9ls2d8c9q-sed-mesboot0-1.18/bin, which in turn contained a working sed:

--8<---------------cut here---------------start------------->8---
Usage: /gnu/store/2z4y0n547x7d566281isklk9ls2d8c9q-sed-mesboot0-1.18/bin/sed [-nV] [--quiet] [--silent] [--version] [-e script]
        [-f script-file] [--expression=script] [--file=script-file] [file…]
--8<---------------cut here---------------end--------------->8---

2. The configure’s shebang (/gnu/store/m89p469fxwn4hj7an9givd1ry9vk7j2l-bash-mesboot0-2.05b/bin/sh) exists on his system and works

This problem has also been encountered in the past: https://logs.guix.gnu.org/guix/2021-04-03.log#210314

As always, I’m happy to spend energy investigating, but would love any pointers on what the most promising place to look is!

Cheers,
Carl Dong
contact@carldong.me
"I fight for the users"



             reply	other threads:[~2021-08-25 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 19:17 Carl Dong [this message]
2021-09-03 10:20 ` bug#50203: binutils-mesboot0: configure: sed: command not found Ludovic Courtès

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=1FF8D553-4B61-400A-AD0B-6A9A0CCFDEA8@carldong.me \
    --to=contact@carldong.me \
    --cc=50203@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.
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).