From: "Ludovic Courtès" <ludo@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: 50203@debbugs.gnu.org
Subject: bug#50203: binutils-mesboot0: configure: sed: command not found
Date: Fri, 03 Sep 2021 12:20:57 +0200 [thread overview]
Message-ID: <878s0e2c52.fsf@gnu.org> (raw)
In-Reply-To: <1FF8D553-4B61-400A-AD0B-6A9A0CCFDEA8@carldong.me> (Carl Dong's message of "Wed, 25 Aug 2021 15:17:26 -0400")
Hi Carl,
Carl Dong <contact@carldong.me> skribis:
> 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
Here’s the relevant excerpt for posterity:
--8<---------------cut here---------------start------------->8---
starting phase `configure'
running ./configure --disable-nls --disable-shared --disable-werror --build=i386-unknown-linux --host=i386-unknown-linux --target=i386-unknown-linux --with-sysroot=/ --prefix=/gnu/store/jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2.14
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 1: sed: command not found
./configure: line 456: rm: command not found
./configure: line 1: sed: command not found
configure: error: can not find sources in or ..
--8<---------------cut here---------------end--------------->8---
> We’ve tried the normal suspects: --cores=1, reboots, mounting tmpfs at /tmp, etc.
Heh. :-)
> 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:
Could you go to the build directory, run “. ../environment-variables”,
and run the configure script like so:
sh -x ./configure …
? That way we’ll see if PATH is getting overridden somewhere.
/gnu/store/2z4y0n547x7d566281isklk9ls2d8c9q-sed-mesboot0-1.18/bin/sed is
a valid i386 static binary AFAICS.
Thanks,
Ludo’.
prev parent reply other threads:[~2021-09-03 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:17 bug#50203: binutils-mesboot0: configure: sed: command not found Carl Dong
2021-09-03 10:20 ` Ludovic Courtès [this message]
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=878s0e2c52.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50203@debbugs.gnu.org \
--cc=contact@carldong.me \
/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).