[U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure

[Bin Meng]

Hi Igor,

On Sat, Nov 2, 2019 at 11:26 PM Igor Opaniuk <igor.opaniuk at gmail.com> wrote:
>
> Hi Bin,
>
> On Sat, Nov 2, 2019 at 3:03 PM Bin Meng <bmeng.cn at gmail.com> wrote:
> >
> > Hi Tom,
> >
> > When I build Simon's patches (the one I applied to u-boot-x86 today),
> > I noticed that the build results for board "tbs2910" in gitlab-ci and
> > azure are different.
> >
> > On gitlab-ci [1], the build fails with error message:
> >
> >        arm:  +   tbs2910
> > +u-boot.imx exceeds file size limit:
> > +  limit:  0x5fc00 bytes
> > +  actual: 0x60c00 bytes
> > +  excess: 0x1000 bytes
> > +make[1]: *** [u-boot.imx] Error 1
> > +make[1]: *** Deleting file 'u-boot.imx'
> > +make: *** [sub-make] Error 2
> >
> >   125  331    1 /701    0:17:40  : tbs2910
> >
> > On azure [2] job "Build the World imx6", the build succeeds:
> >
> >        arm:  w+   tbs2910
> > +===================== WARNING ======================
> > +This board does not use CONFIG_DM_VIDEO Please update
> > +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> > +Failure to update by the deadline may result in board removal.
> > +See doc/driver-model/MIGRATION.txt for more info.
> > +====================================================
> > +CONFIG_OF_EMBED is enabled. This option should only
> > +be used for debugging purposes. Please use
> > +CONFIG_OF_SEPARATE for boards in mainline.
> > +See doc/README.fdt-control for more info.
> >
> >     6   24    0 /55     0:07:44  : tbs2910
> >
> > I am not sure what might be the problem. Do you know what could be the cause?
> >
> > [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> > [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
> >
> > Regards,
> > Bin
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > https://lists.denx.de/listinfo/u-boot
>
> That is toolchain version specific issue(there was a discussion about
> this board [1]).
>

Thanks for checking.

> On Azure gcc-9.1.0-2 is used
> In gitlab-ci - gcc-7.3.0.
>

But I don't understand why this is caused by GCC version. Azure is
using the same CI runner docker image used by gitlab-ci so compiler
version should be the same.

> [1] https://patchwork.ozlabs.org/patch/1180025/
>

Regards,
Bin