[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Thomas Petazzoni]

Hello,

The radxa_rock_pi4_defconfig in Buildroot doesn't build:

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

When building ATF, it fails with:

arm-none-eabi-gcc -g -mcpu=cortex-m0 -mthumb -Wall -O3 -nostdlib -mfloat-abi=soft -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common -Iinclude/ -I../../include/shared/ -MMD -MT /builds/buildroot.org/buildroot/output/build/arm-trusted-firmware-v2.0/build/rk3399/release/m0/dram.o -c src/dram.c -o /builds/buildroot.org/buildroot/output/build/arm-trusted-firmware-v2.0/build/rk3399/release/m0/dram.o 
make[2]: arm-none-eabi-gcc: Command not found

It seems like it tries to build some code for a Cortex-M0 co-processor,
with the arm-none-eabi-gcc toolchain, which is not available.

I believe this is a common problem: we are building for a AArch64
system, but some bits of the firmware need to be built for an ARM
32-bit co-processor, and this requires a separate toolchain. I know
there is the same problem when building ATF for the Marvell Armada 3720
SoC.

The only solution that I can see is to create a separate package (a
regular package, not a toolchain package) that installs in $(HOST_DIR)
a bare-metal ARM 32 bit toolchain. Then the ATF package needs to be
adjusted so that it can optionally depend on such a package, and pass
the appropriate flags to tell ATF the prefix of that toolchain.

Would you be willing to work on that ? It would be good to make sure it
also works for the Marvell Armada 3720 case.

You can look at
http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
where a previous proposal was made, and which was reviewed.
Unfortunately, the author never came back with a second iteration of
the patch series.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Thomas Petazzoni]

Hello,

On Sat, 10 Aug 2019 14:36:35 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> The radxa_rock_pi4_defconfig in Buildroot doesn't build:
> 
> https://gitlab.com/buildroot.org/buildroot/-/jobs/269139271

The pine64_rockpro64_defconfig is affected by the same issue:

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

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Thomas Petazzoni]

Hello,

On Sat, 10 Aug 2019 14:39:30 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> The pine64_rockpro64_defconfig is affected by the same issue:
> 
>   https://gitlab.com/buildroot.org/buildroot/-/jobs/269139227

More in the same situation:

 * nanopi_neo4_defconfig:

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

 * nanopi_m4_defconfig

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

 * nanopc_t4_defconfig

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

So, it is really urgent to fix this issue. If it isn't fixed for the
2019.08 release (end of August), we will have to remove those
defconfigs, at least for now.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Jagan Teki]

Hi Thomas,

On Sat, Aug 10, 2019 at 6:06 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> The radxa_rock_pi4_defconfig in Buildroot doesn't build:
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/269139271
>
> When building ATF, it fails with:
>
> arm-none-eabi-gcc -g -mcpu=cortex-m0 -mthumb -Wall -O3 -nostdlib -mfloat-abi=soft -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common -Iinclude/ -I../../include/shared/ -MMD -MT /builds/buildroot.org/buildroot/output/build/arm-trusted-firmware-v2.0/build/rk3399/release/m0/dram.o -c src/dram.c -o /builds/buildroot.org/buildroot/output/build/arm-trusted-firmware-v2.0/build/rk3399/release/m0/dram.o
> make[2]: arm-none-eabi-gcc: Command not found
>
> It seems like it tries to build some code for a Cortex-M0 co-processor,
> with the arm-none-eabi-gcc toolchain, which is not available.
>
> I believe this is a common problem: we are building for a AArch64
> system, but some bits of the firmware need to be built for an ARM
> 32-bit co-processor, and this requires a separate toolchain. I know
> there is the same problem when building ATF for the Marvell Armada 3720
> SoC.
>
> The only solution that I can see is to create a separate package (a
> regular package, not a toolchain package) that installs in $(HOST_DIR)
> a bare-metal ARM 32 bit toolchain. Then the ATF package needs to be
> adjusted so that it can optionally depend on such a package, and pass
> the appropriate flags to tell ATF the prefix of that toolchain.
>
> Would you be willing to work on that ? It would be good to make sure it
> also works for the Marvell Armada 3720 case.

Yes, installing arm32 cross tool would work since the ATF here on
rockchip does require 32 and 64 tool-chains. I can confirm it with my
build just know.

>
> You can look at
> http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
> where a previous proposal was made, and which was reviewed.
> Unfortunately, the author never came back with a second iteration of
> the patch series.

Will check with this series and get back to you as soon as possible.

Thanks for noticing, I thought that this was fixed before.

Jagan.

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Thomas Petazzoni]

Hello Jagan,

On Sun, 11 Aug 2019 10:07:15 +0530
Jagan Teki <jagan@amarulasolutions.com> wrote:

> > You can look at
> > http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
> > where a previous proposal was made, and which was reviewed.
> > Unfortunately, the author never came back with a second iteration of
> > the patch series.  
> 
> Will check with this series and get back to you as soon as possible.
> 
> Thanks for noticing, I thought that this was fixed before.

Thanks for your feedback. Do you think you will have the chance to look
into this this week ?

I'm wondering what to do with those defconfigs in preparation for our
2019.08 release. I think the safest is probably to remove them, and
reintroduce them once we have a proper solution for the arm32
toolchain. It seems a bit late to merge a solution for this during this
cycle.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds

[Shyam Saini]

Hi Thomas,




On Sun, Aug 18, 2019, 12:50 PM Thomas Petazzoni <
thomas.petazzoni@bootlin.com> wrote:

> Hello Jagan,
>
> On Sun, 11 Aug 2019 10:07:15 +0530
> Jagan Teki <jagan@amarulasolutions.com> wrote:
>
> > > You can look at
> > > http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
> > > where a previous proposal was made, and which was reviewed.
> > > Unfortunately, the author never came back with a second iteration of
> > > the patch series.
> >
> > Will check with this series and get back to you as soon as possible.
> >
> > Thanks for noticing, I thought that this was fixed before.
>
> Thanks for your feedback. Do you think you will have the chance to look
> into this this week ?
>

I will send patch this week.


Thanks,
Shyam


> I'm wondering what to do with those defconfigs in preparation for our
> 2019.08 release. I think the safest is probably to remove them, and
> reintroduce them once we have a proper solution for the arm32
> toolchain. It seems a bit late to merge a solution for this during this
> cycle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190818/f7f5c913/attachment.html>