unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Carl Dong <contact@carldong.me>
Cc: 49985@debbugs.gnu.org
Subject: bug#49985: bash-mesboot0: Inscrutable error in build phase
Date: Wed, 11 Aug 2021 14:53:17 +0200	[thread overview]
Message-ID: <20210811125317.GA49029@LionPure> (raw)
In-Reply-To: <20210811012118.GB26014@LionPure>

Just this disclaimer:
I am just a lurker interested in mes, not a mes developer or team member.
(I am trying to do some minimal stuff too, so I cloned the mes repo and pull once
in a while to see what's going on :)

Sorry for any implication that I really know anything about mes ;/

On +2021-08-11 03:21:18 +0200, Bengt Richter wrote:
> On +2021-08-11 02:38:54 +0200, Bengt Richter wrote:
> > On +2021-08-10 15:41:25 -0400, Carl Dong wrote:
> > > Hi all,
> > > 
> > > While setting up Guix for a community member of mine, we encountered this somewhat inscrutable problem (I later learned this is not the first time Guix users have run into this problem!). When building /gnu/store/2nvaxgs0rdxfkrwklh622ggaxg0wap6n-bash-mesboot0-2.05b.drv, we encountered the following build failure: https://paste.sr.ht/~dongcarl/376b19b8349c329ed5329508c7fb43a7c3aec64b#2nvaxgs0rdxfkrwklh622ggaxg0wap6n-bash-mesboot0-2.05b.log-L1299
> > > 
> > > The error line is L1299: "make: stat:Makefile: sterror: unknown error”
> > >--
> > 
> > To me, sterror looks like a typo for strerror
> > so grepping for sterror might find the typo, if that's what it is?
> >
> Looking at ./lib/mes/__mes_debug.c, it looks like you could set/export environment
>  MES_DEBUG=1 and run it again to see the error number ./lib/string/strerror.c
> (in git repo) doesn't like.
> 
> Then run something like my error-printing kludge that will work on your system:
> 
> I called it errno-grep
> --8<---------------cut here---------------start------------->8---
> #!/usr/bin/bash
> if [ -z "$1" ];then
>     echo "Usage: errno-grep [ grep switches for grepping the following files in order ]"
>     echo "    /usr/include/asm-generic/errno-base.h"
>     echo "    /usr/include/asm-generic/errno.h"
>     exit 0
> fi
> 
> if [ "${1:0:1}" == "-" ]; then
>     exec grep "$@" /usr/include/asm-generic/errno-base.h /usr/include/asm-generic/errno.h
> else
>     exec egrep -wh "$@" /usr/include/asm-generic/errno-base.h /usr/include/asm-generic/errno.h
> fi
> --8<---------------cut here---------------end--------------->8---
> 
> HTH.
> 
> 
> 

-- 
Regards,
Bengt Richter




  reply	other threads:[~2021-08-11 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 19:41 bug#49985: bash-mesboot0: Inscrutable error in build phase Carl Dong
2021-08-11  0:38 ` Bengt Richter
2021-08-11  1:21   ` Bengt Richter
2021-08-11 12:53     ` Bengt Richter [this message]
2021-08-12 17:04       ` Carl Dong
2021-08-19 16:20 ` Mathieu Othacehe
2021-08-25 18:37   ` Carl Dong

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=20210811125317.GA49029@LionPure \
    --to=bokr@bokr.com \
    --cc=49985@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).