[Buildroot] defconfig build issues

[Buildroot] defconfig build issues

[Thomas Petazzoni]

Hello,

The following defconfigs are failing to build currently:

  freescale_imx6sololiteevk_defconfig
  freescale_imx31_3stack_defconfig
  freescale_imx6ulevk_defconfig
  s6lx9_microboard_defconfig
  socrates_cyclone5_defconfig
  raspberrypi3_qt5we_defconfig

If you are interested in keeping those defconfigs in Buildroot, please
see below the details of the failures. I propose that any defconfig
that isn't fixed by 2018.05-rc2 will be removed from Buildroot.

freescale_imx6sololiteevk_defconfig
===================================

Error: No BOOT_FROM tag in board/freescale/mx6slevk/imximage.cfg.cfgtmp
arch/arm/imx-common/Makefile:91: recipe for target 'u-boot-dtb.imx' failed

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561693

I think this has already been fixed in other defconfigs.

freescale_imx31_3stack_defconfig
================================

arch/arm/mach-imx/built-in.o: In function `init_mmdc_lpddr2_settings':
platform-spi_imx.c:(.text+0x8f18): undefined reference to `imx6sll_lpddr2_freq_change'
arch/arm/mach-imx/built-in.o: In function `imx6ul_cpuidle_init':
platform-spi_imx.c:(.init.text+0x195c): undefined reference to `mx6ull_lpm_wfi_end'
platform-spi_imx.c:(.init.text+0x1960): undefined reference to `mx6ull_lpm_wfi_start'
platform-spi_imx.c:(.init.text+0x1964): undefined reference to `imx6ull_low_power_idle'
arch/arm/mach-imx/built-in.o: In function `imx6sl_init_late':
platform-spi_imx.c:(.init.text+0x56f0): undefined reference to `imx6sll_cpuidle_init'
Makefile:969: recipe for target 'vmlinux' failed

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561688

I've already reported this a while ago. Any fix coming in the near future ?

freescale_imx6ulevk_defconfig
=============================

./scripts/dtc-version.sh: line 17: dtc: command not found
./scripts/dtc-version.sh: line 18: dtc: command not found
*** Your dtc is too old, please upgrade to dtc 1.4 or newer

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561695

This one is easy: U-Boot needs DTC, just one option to add in the defconfig.

s6lx9_microboard_defconfig
==========================

make[1]: *** No rule to make target 'simpleImage.'.  Stop.

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561794

No idea about this one. I don't think it was failing before, and I
don't think this defconfig has been changed recently. Do we have a
regression in the Linux kernel build logic ?

socrates_cyclone5_defconfig
===========================

Could not fetch special ref 'rel_socfpga-4.1.33-ltsi_17.07.02_pr'; assuming it is not special.
error: pathspec 'rel_socfpga-4.1.33-ltsi_17.07.02_pr' did not match any file(s) known to git.

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561801

The Linux kernel tag being used in the defconfig no longer exists.

raspberrypi3_qt5we_defconfig
============================

Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
For other distributions, refer to their documentation.

https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791

This defconfig includes WebKit, which wants a C++ multilib compiler on
the host, which isn't present in our Docker image used for the gitlab
CI builds. Should we add this to our Docker image ? Should we exclude
this defconfig from the gitlab CI testing ?

Thanks for your support,

Thomas Petazzoni
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] defconfig build issues

[Fabio Estevam]

Hi Thomas,

On Sat, May 5, 2018 at 4:52 PM, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:

> freescale_imx6sololiteevk_defconfig
> ===================================
>
> Error: No BOOT_FROM tag in board/freescale/mx6slevk/imximage.cfg.cfgtmp
> arch/arm/imx-common/Makefile:91: recipe for target 'u-boot-dtb.imx' failed
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/66561693
>
> I think this has already been fixed in other defconfigs.

Yes, this has been fixed in U-Boot mainline.

I think I will send a patch removing this target as we have a
imx6ulevk_defconfig target that is based on U-Boot and kernel
mainline.

I prefer to maintain the mainline version rather than the target based
on NXP U-Boot and kernel versions.

> freescale_imx31_3stack_defconfig
> ================================
>
> arch/arm/mach-imx/built-in.o: In function `init_mmdc_lpddr2_settings':
> platform-spi_imx.c:(.text+0x8f18): undefined reference to `imx6sll_lpddr2_freq_change'
> arch/arm/mach-imx/built-in.o: In function `imx6ul_cpuidle_init':
> platform-spi_imx.c:(.init.text+0x195c): undefined reference to `mx6ull_lpm_wfi_end'
> platform-spi_imx.c:(.init.text+0x1960): undefined reference to `mx6ull_lpm_wfi_start'
> platform-spi_imx.c:(.init.text+0x1964): undefined reference to `imx6ull_low_power_idle'
> arch/arm/mach-imx/built-in.o: In function `imx6sl_init_late':
> platform-spi_imx.c:(.init.text+0x56f0): undefined reference to `imx6sll_cpuidle_init'
> Makefile:969: recipe for target 'vmlinux' failed
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/66561688
>
> I've already reported this a while ago. Any fix coming in the near future ?

The 4.9 NXP kernel does not support mx31. I don't have access to this
board, so I will send a patch removing it.

If someone is interested on this board, then a patch adding a
defconfig based on U-Boot and kernel mainline can be added later.

>
> freescale_imx6ulevk_defconfig
> =============================
>
> ./scripts/dtc-version.sh: line 17: dtc: command not found
> ./scripts/dtc-version.sh: line 18: dtc: command not found
> *** Your dtc is too old, please upgrade to dtc 1.4 or newer
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/66561695
>
> This one is easy: U-Boot needs DTC, just one option to add in the defconfig.

Same here. Will drop this one as we have imx6ulevk_defconfig target
which uses mainline U-Boot and kernel.

[Buildroot] defconfig build issues

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 > s6lx9_microboard_defconfig
 > ==========================

 > make[1]: *** No rule to make target 'simpleImage.'.  Stop.

 > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561794

 > No idea about this one. I don't think it was failing before, and I
 > don't think this defconfig has been changed recently. Do we have a
 > regression in the Linux kernel build logic ?

Yes, looks like it. The make target it tries to call is
'simpleImage. lx9_mmu', E.G. a space has been added before the list of
dtbs. I've sent a patch fixing it.

 > raspberrypi3_qt5we_defconfig
 > ============================

 > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
 > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
 > For other distributions, refer to their documentation.

 > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791

 > This defconfig includes WebKit, which wants a C++ multilib compiler on
 > the host, which isn't present in our Docker image used for the gitlab
 > CI builds. Should we add this to our Docker image ? Should we exclude
 > this defconfig from the gitlab CI testing ?

I would say yes, we want the defconfigs to be tested.

-- 
Bye, Peter Korsgaard

[Buildroot] defconfig build issues

[Martin Bark]

Hi,

On 6 May 2018 at 07:34, Peter Korsgaard <peter@korsgaard.com> wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>
> Hi,
>
>  > s6lx9_microboard_defconfig
>  > ==========================
>
>  > make[1]: *** No rule to make target 'simpleImage.'.  Stop.
>
>  > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561794
>
>  > No idea about this one. I don't think it was failing before, and I
>  > don't think this defconfig has been changed recently. Do we have a
>  > regression in the Linux kernel build logic ?
>
> Yes, looks like it. The make target it tries to call is
> 'simpleImage. lx9_mmu', E.G. a space has been added before the list of
> dtbs. I've sent a patch fixing it.
>
>  > raspberrypi3_qt5we_defconfig
>  > ============================
>
>  > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
>  > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
>  > For other distributions, refer to their documentation.
>
>  > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791

support/docker/Dockerfile already installs g++-multilib but the image
buildroot/base:20180205.0730 lacks it.  It looks like g++-multilib was
added just after the image was created in commit
27d22296927d7e4ec0965f2bdaa272b1e8ea15e7

So i think this should already be fixed, you just need to update the
buildroot/base image

Thanks

Martin

>
>  > This defconfig includes WebKit, which wants a C++ multilib compiler on
>  > the host, which isn't present in our Docker image used for the gitlab
>  > CI builds. Should we add this to our Docker image ? Should we exclude
>  > this defconfig from the gitlab CI testing ?
>
> I would say yes, we want the defconfigs to be tested.
>
> --
> Bye, Peter Korsgaard

[Buildroot] defconfig build issues

[Arnout Vandecappelle]

On 06-05-18 15:50, Martin Bark wrote:
> Hi,
> 
> On 6 May 2018 at 07:34, Peter Korsgaard <peter@korsgaard.com> wrote:
>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
[snip]
>>  > raspberrypi3_qt5we_defconfig
>>  > ============================
>>
>>  > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
>>  > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
>>  > For other distributions, refer to their documentation.
>>
>>  > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791
> 
> support/docker/Dockerfile already installs g++-multilib but the image
> buildroot/base:20180205.0730 lacks it.  It looks like g++-multilib was
> added just after the image was created in commit
> 27d22296927d7e4ec0965f2bdaa272b1e8ea15e7
> 
> So i think this should already be fixed, you just need to update the
> buildroot/base image

 Or rather, 12b08c2be639e26ba0983d7dbdb3bddd91355f4c should be backported to
2018.02.

 Regards,
 Arnout

> 
> Thanks
> 
> Martin
> 
>>
>>  > This defconfig includes WebKit, which wants a C++ multilib compiler on
>>  > the host, which isn't present in our Docker image used for the gitlab
>>  > CI builds. Should we add this to our Docker image ? Should we exclude
>>  > this defconfig from the gitlab CI testing ?
>>
>> I would say yes, we want the defconfigs to be tested.
>>
>> --
>> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] defconfig build issues

[Peter Korsgaard]

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 06-05-18 15:50, Martin Bark wrote:
 >> Hi,
 >> 
 >> On 6 May 2018 at 07:34, Peter Korsgaard <peter@korsgaard.com> wrote:
 >>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
 > [snip]
 >>> > raspberrypi3_qt5we_defconfig
 >>> > ============================
 >>> 
 >>> > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
 >>> > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
 >>> > For other distributions, refer to their documentation.
 >>> 
 >>> > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791
 >> 
 >> support/docker/Dockerfile already installs g++-multilib but the image
 >> buildroot/base:20180205.0730 lacks it.  It looks like g++-multilib was
 >> added just after the image was created in commit
 >> 27d22296927d7e4ec0965f2bdaa272b1e8ea15e7
 >> 
 >> So i think this should already be fixed, you just need to update the
 >> buildroot/base image

 >  Or rather, 12b08c2be639e26ba0983d7dbdb3bddd91355f4c should be backported to
 > 2018.02.

Ahh - Committed to 2018.02.x, thanks.

-- 
Bye, Peter Korsgaard