Hi!

Have you experienced anything like this while compiling from the branch 4.8.1?
I have a fresh and a ~ 1 year old crossgcc pack, but both are end up
after a make menuconfig ; make -j8 with the same way.
In the latest crossgcc build, I had to apply an include string fix to
binutils and a -Wl,--allow-multiple-definition to the acpica's
LDFLAGS.
####
$ CC=/usr/bin/gcc make -d -j8
GNU Make 4.3
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Reading makefile 'Makefile'...
Reading makefile '/media/ramdisk/coreboot/util/kconfig/Makefile'
(search path) (no ~ expansion)...
Reading makefile '/media/ramdisk/coreboot/.config' (search path) (no ~
expansion)...
Reading makefile '.xcompile' (search path) (don't care) (no ~ expansion)...
Reading makefile 'toolchain.inc' (search path) (no ~ expansion)...
Reading makefile 'Makefile.inc' (search path) (don't care) (no ~ expansion)...
Skipping submodule '3rdparty/blobs'
Reading makefile 'util/crossgcc/Makefile.inc' (search path) (no ~ expansion)...
.
.
Reading makefile 'src/vendorcode/amd/pi/00670F00/Makefile.inc' (search
path) (don't care) (no ~ expansion)...
Segmentation error (core dumped)
####
$ dmesg | tail -1
[30582.804975] make[750110]: segfault at 7fffb5d2dff8 ip
00007fd105838cff sp 00007fffb5d2e000 error 6 in
libc-2.32.so[7fd1057d3000+14d000]
[30582.804983] Code: 00 00 00 48 3b 1d 51 64 13 00 0f 82 ab 00 00 00
64 8b 04 25 18 00 00 00 85 c0 0f 85 23 01 00 00 48 89 ee 48 8d 3d 01
6d 13 00 <e8> cc e2 ff ff 49 89 c0 48 85 c0 0f 84 c8 00 00 00 48 8b 40
f8 a8
####

Do you have any ideas? I'm using Arch Linux 5.9 with GCC 10.2
I had a try on another machine with Arch Linux 4.19 LTS@GCC 10.2

Thanks
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to