I've been working on testing current coreboot on my asus/p2b and
asus/p2-99 for the upcoming release, but ran in to problems trying to
build it on my p2b with Gentoo with gcc 11.2.0. It (ironically) did
build and work on the p2-99 with Debian Buster (oldstable) with gcc
8.3.0. It also built on my main system with Debian sid 64bit and gcc
11.2.0.
CC host/lib/extract_vmlinuz.o
In file included from /usr/include/string.h:519,
from host/lib/extract_vmlinuz.c:9:
In function 'memcpy',
inlined from 'ExtractVmlinuz' at host/lib/extract_vmlinuz.c:67:2:
/usr/include/bits/string_fortified.h:29:10: error: '__builtin_memcpy'
specified bound between 2147483648 and 4294967295 exceeds maximum
object size 2147483647 [-Werror=stringop-overflow=]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
host/lib/extract_vmlinuz.c: At top level:
cc1: note: unrecognized command-line option '-Wno-unknown-warning' may
have been intended to silence earlier diagnostics
cc1: all warnings being treated as errors
It looks like I might have to do a better job of regular testing of
self hosting the build on these old 32-bit systems.
Branden
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
