All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig)
Date: Thu, 6 Apr 2017 18:32:18 +0200	[thread overview]
Message-ID: <20170406183218.66cab07e@free-electrons.com> (raw)
In-Reply-To: <CAOf5uwkL9FX3Fq2Dou1jnixat2CWxtWSbXG+Q=RQ=y3pSyjRzA@mail.gmail.com>

Hello,

On Thu, 6 Apr 2017 18:12:15 +0200, Michael Nazzareno Trimarchi wrote:

> '/home/michael/work/amarula/bticino/buildroot/output/build/linux-52c4aa7cdb93d61f8008f380135beaf7b8fa6593'
>   DTC     arch/arm/boot/dts/am335x-bone.dtb
>   DTC     arch/arm/boot/dts/am335x-evm.dtb
> make[2]: *** No rule to make target
> 'arch/arm/boot/dts/am335x-bonegreen.dtb'.  Stop.
> arch/arm/Makefile:314: recipe for target 'am335x-bonegreen.dtb' failed

This is caused by the recent commit
https://git.buildroot.org/buildroot/commit/configs?id=4b2440b7dcc68369548c0f2be6984fe645fc6bb0
from Matthias Fritzsche. Matthias, are you sure you tested the
beaglebone_qt5_defconfig ?

Indeed, beaglebone_defconfig and beaglebone_qt5_defconfig don't use the
same kernel version, and the one used in beaglebone_qt5_defconfig
doesn't have the Beagle Bone Green Device Tree.

So either we should revert Matthias patch on beaglebone_qt5_defconfig,
or someone tests upgrading beaglebone_qt5_defconfig to the same kernel
version as the one used in beaglebone_defconfig.

> chmod a+x /home/michael/work/amarula/bticino/buildroot/output/build/_fakeroot.fs
> PATH="/home/michael/work/amarula/bticino/buildroot/output/host/bin:/home/michael/work/amarula/bticino/buildroot/output/host/sbin:/home/michael/work/amarula/bticino/buildroot/output/host/usr/bin:/home/michael/work/amarula/bticino/buildroot/output/host/usr/sbin:/opt/OpenPrinting-Gutenprint/sbin:/opt/OpenPrinting-Gutenprint/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/java-7-oracle/bin:/usr/lib/jvm/java-7-oracle/db/bin:/usr/lib/jvm/java-7-oracle/jre/bin"
> /home/michael/work/amarula/bticino/buildroot/output/host/usr/bin/fakeroot
> -- /home/michael/work/amarula/bticino/buildroot/output/build/_fakeroot.fs
> rootdir=/home/michael/work/amarula/bticino/buildroot/output/target
> table='/home/michael/work/amarula/bticino/buildroot/output/build/_device_table.txt'
> genext2fs: couldn't allocate a block (no free space)
> fs/ext2/ext2.mk:44: recipe for target

This is due to the fact that we removed auto-calculation of the ext4
filesystem size in
https://git.buildroot.org/buildroot/commit/?id=c6bca8cef0310bc649240b451989457ce94a8358,
and we default to 60 MB for the filesystem size, which is not enough
for this demo. Fixing this is simple: send a patch that adds:

BR2_TARGET_ROOTFS_EXT2_BLOCKS="126976"

to beaglebone_qt5_defconfig (of course after testing that this size is
sufficient).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-06 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 10:57 [Buildroot] Qt5 build failure (beaglebone_qt5_defconfig) Arnout Vandecappelle
2017-04-06 11:47 ` Peter Seiderer
2017-04-06 16:12   ` Michael Nazzareno Trimarchi
2017-04-06 16:32     ` Thomas Petazzoni [this message]
2017-04-06 16:57       ` Thomas Petazzoni
2017-04-07  7:54         ` Michael Trimarchi
2017-04-07  8:06           ` Thomas Petazzoni
2017-04-07  8:09             ` Michael Trimarchi
2017-04-07  8:19               ` Thomas Petazzoni
2017-04-06 21:27       ` txt.file
2017-04-07  7:28       ` Michael Nazzareno Trimarchi
2017-04-06 16:33   ` Thomas Petazzoni
2017-04-07 18:47     ` Peter Seiderer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170406183218.66cab07e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.