bug#45165: binutils-mesboot0 fails at configure, cannot find lex

[Ludovic Courtès]

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’.