[Buildroot] Analysis of defconfig build failures

Luca Ceresoli luca at lucaceresoli.net
Tue Aug 28 08:07:30 UTC 2018


Hi,

On 27/08/2018 23:19, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot at gmail.com> writes:
> 
> Hi,
> 
>  > Backtrace from a quick gdb session:
> 
>  > Program received signal SIGABRT, Aborted.
>  > 0x00007ffff7a4b010 in raise () from /lib64/libc.so.6
>  > (gdb) bt
>  > #0  0x00007ffff7a4b010 in raise () from /lib64/libc.so.6
>  > #1  0x00007ffff7a4cc0d in abort () from /lib64/libc.so.6
>  > #2  0x00007ffff7a427e7 in ?? () from /lib64/libc.so.6
>  > #3  0x00007ffff7a428a2 in __assert_fail () from /lib64/libc.so.6
>  > #4  0x0000555555560a6f in propval_cell ()
>  > #5  0x000055555555b536 in check_graph_child_address ()
>  > #6  0x0000555555558dc8 in check_nodes_props ()
>  > #7  0x0000555555558df6 in check_nodes_props ()
>  > #8  0x000055555555a4d7 in run_check ()
>  > #9  0x000055555555c2cf in process_checks ()
>  > #10 0x0000555555558797 in main ()
> 
>  > I haven't dug deeper. It could be that some patching is needed in
>  > host-dtc itself, to solve the above error.
> 
> Thanks for investigating. This again seems to confirm that reverting the
> dtc bump will be a solution for 2018.08.

At any rate, I just sent a small series to upgrade U-Boot for 3 zynq
boards. Even with the dtc bump revert they shouldn't hurt.

Regards,
-- 
Luca



More information about the buildroot mailing list