all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Hiller <thrilleratplay@gmail.com>
To: 45165@debbugs.gnu.org
Subject: bug#45165: binutils-mesboot0 fails at configure, cannot find lex
Date: Fri, 25 Dec 2020 10:57:10 -0500	[thread overview]
Message-ID: <c47725a0-79b0-edfe-ae50-9120acabc7f6@gmail.com> (raw)
In-Reply-To: <1C1332EB-3389-416F-A8A7-0CF6A469AE29@carldong.me>

I also started to see this issue a few days ago.  The host is currently 
running a variant of Linux 5.9.14-arch1-1 and the docker image is 
Alpine:3.12.  I am not sure if this is helpful but if I remember 
correctly, I rebooted my machine in between the times I was last able to 
binutils-mesboot0 which probably loaded  Linux 5.9.14-arch1-1 into 
memory.  Before it would have been using Linux 5.9.11-arch2 
configuration.  Given the timeline, a change in Linux 5.9.12 or Linux 
5.9.13 may be the cause.





  parent reply	other threads:[~2020-12-25 20:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 20:01 bug#45165: binutils-mesboot0 fails at configure, cannot find lex Carl Dong
2020-12-10 22:28 ` Carl Dong
2020-12-11  6:33   ` Jan Nieuwenhuizen
2020-12-11 16:37     ` Carl Dong
2020-12-15 18:50       ` Carl Dong
2020-12-16  0:46         ` Carl Dong
2020-12-16 17:49           ` Carl Dong
2020-12-22 14:33           ` Ludovic Courtès
2020-12-22 16:42             ` Carl Dong
2021-01-18 22:48             ` Carl Dong
2021-01-19 23:03               ` Carl Dong
2021-02-03 19:18                 ` Carl Dong
2021-02-06 21:04                   ` Ludovic Courtès
2020-12-25 15:57 ` Tom Hiller [this message]
2021-02-27 10:33 ` Vincent Legoll
2021-06-09 13:36 ` kitzman via Bug reports for GNU Guix
2021-06-09 15:12   ` kitzman via Bug reports for GNU Guix
2021-12-24  5:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-12-24  8:11   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-02-24 13:09     ` kitzman via Bug reports for GNU Guix

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c47725a0-79b0-edfe-ae50-9120acabc7f6@gmail.com \
    --to=thrilleratplay@gmail.com \
    --cc=45165@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.