unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
Cc: 45165@debbugs.gnu.org
Subject: bug#45165: binutils-mesboot0 fails at configure, cannot find lex
Date: Fri, 24 Dec 2021 09:11:58 +0100	[thread overview]
Message-ID: <8735mih0r6.fsf@nckx> (raw)
In-Reply-To: <87pmpmttar.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

Tobias Geerinckx-Rice via Bug reports for GNU Guix 写道:
> My diff from linux-libre, which sure seems to tell a story:
>
> y -> not set  CONFIG_UID16 (obsolete)

As expected upthread, this and this alone was indeed the culprit. 
I don't see any evidence of interaction with other options though.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-12-24  8:21 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
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 [this message]
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

  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=8735mih0r6.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=45165@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).