[SeaBIOS] Mysterious "is VARVERIFY32INIT but used from" problem while trying to improve SeaBIOS

[Mike Banon]

"varverify32init.patch" in the attachments. To apply a patch please copy it
to the coreboot directory, "cd" to coreboot, and - if seabios is already cloned
(e.g. after building a coreboot once, followed by a "make clean" of course)
run " patch -l -p1 < varverify32init.patch "

Sorry, my previous message had a typo, the final results for testfunc() :

(1) = OK, inside " cbfs_copyfile "
(2) = OK, inside " coreboot_cbfs_init "
(3) = ERR, inside " cbfs_run_payload "

P.S. I'm using the default "menuconfig" settings, "emulation/qemu-i440fx" target

Best regards,
Mike

On Sun, Feb 25, 2018 at 11:55 AM, Paul Menzel <pmenzel at molgen.mpg.de> wrote:
> Dear Mike,
>
>
> Am 25.02.2018 um 01:05 schrieb Mike Banon:
>>
>> Friends, I need your help. While trying to improve SeaBIOS I got stuck
>> at this very strange problem - which does not appear when you do a
>> standalone build of SeaBIOS but it happens when you try building a
>> coreboot together with SeaBIOS. Steps to reproduce:
>
>
> Please attach your patch, so that it can easily applied and the build
> problem reproduced.
>
> […]
>
>
> Kind regards,
>
> Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: varverify32init.patch
Type: text/x-patch
Size: 1583 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/seabios/attachments/20180225/54711188/attachment.patch>