From: "Ludovic Courtès" <ludo@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: 45165@debbugs.gnu.org
Subject: bug#45165: binutils-mesboot0 fails at configure, cannot find lex
Date: Sat, 06 Feb 2021 22:04:46 +0100 [thread overview]
Message-ID: <875z3429ht.fsf@gnu.org> (raw)
In-Reply-To: <9F85A050-2C47-422D-840C-EFD0EBA7B06B@carldong.me> (Carl Dong's message of "Wed, 3 Feb 2021 14:18:08 -0500")
Hi,
Carl Dong <contact@carldong.me> skribis:
> New observation! On my Arch machine which has
>
> 5.10.11-arch1-1
>
> And
>
> # CONFIG_EXPERT is not set
> CONFIG_UID16=y
>
> (So according to my previous email it not trigger the bug)
>
> I’m getting the following strace:
>
> $ strace -v -e trace=file ~/sh -c "test -w /home/dongcarl/.bash_profile”
> execve(<blahblah>) = 0
> [ Process PID=404360 runs in 32 bit mode. ]
> open("/dev/tty", O_RDWR) = 3
> stat("/home/dongcarl", 0xffdcd738) = -1 EOVERFLOW (Value too large for defined data type)
> getcwd("/home/dongcarl", 1024) = 15
> stat("/home/dongcarl/.bash_profile", 0xffdcd6bc) = -1 EOVERFLOW (Value too large for defined data type)
> +++ exited with 1 +++
>
> Not sure hot to interpret this...
It would seem that CONFIG_UID16=y is the culprit after all, no?
Is there a way we can detect kernel misconfiguration and that does not
involve /proc/config.gz?
If not, perhaps we could do precisely the test above in one of the early
derivations in commencement.scm: run “sh -c 'test -w /'” and fail right
away if that doesn’t work.
WDYT?
Ludo’.
next prev parent reply other threads:[~2021-02-06 21:05 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 [this message]
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
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=875z3429ht.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45165@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).