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

2021-06-09 Thread kitzman via Bug reports for GNU Guix
Dear all, I have ran into the exact same issue (I will assume it's the same source). I suppose this is only relevant for certain forks of the kernel, not the mainline one - I also assume that my train thought might prove useful... hopefully. * Syscalls * The stat syscall works - but then bash t

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

2021-06-09 Thread kitzman via Bug reports for GNU Guix
Please ignore the following. A function appearing there can still return ENOSYS. kitzman writes: > A quick way to check this is to cat "/proc/kallsyms", look for > "__ia32_sys_getuid", and see where (and if) it's mapped in memory. > For me, it's not, ergo, the syscalls are not implemented, thus

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

2022-02-24 Thread kitzman via Bug reports for GNU Guix
Tobias Geerinckx-Rice writes: >> 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. > I tried working