All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] sunxi-boards: set a default board
Date: Wed, 5 Jun 2013 21:38:07 +0200	[thread overview]
Message-ID: <20130605213807.0c015c5d@skate> (raw)
In-Reply-To: <87d2s0cqtw.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Wed, 05 Jun 2013 21:14:51 +0200, Peter Korsgaard wrote:

>  Thomas> The default configuration doesn't set any board, but the
>  Thomas> sunxi-boards.mk file errors out if no board is defined. This causes a
>  Thomas> large number of build failures in the autobuilders, such as
>  Thomas> http://autobuild.buildroot.org/results/b92/b928edc07f0939531d76833a17c851889ae06677/build-end.log.
> 
>  Thomas> The proposed approach to solve this is to set a default board. An
>  Thomas> alternative approach would have been to remove the check that ensures
>  Thomas> that a board has been set, but I believe it's less obvious for the
>  Thomas> user.
> 
> That won't help as it then just fails when it tries to build/install.

Well, we could tune the build/install step to not fail if
BR2_PACKAGE_SUNXI_BOARDS_FEX_FILE is empty, but I don't think we want
to do that.

> Hmm, how is this different that what we do for the barebox/u-boot/linux
> configurations?

It is different in that this package starts with BR2_PACKAGE, so it can
get selected by the randpackageconfig logic, while barebox/u-boot/linux
Kconfig options don't start by BR2_PACKAGE, so they don't get selected
by randpackageconfig :)

> If people forget to set a sensible _FEX_FILE they now silently get the
> wrong stuff (if they don't build for hackberry) instead of a clear error
> message.

Right.

> Wouldn't it make more sense to blacklist the package or preseed
> BR2_PACKAGE_SUNXI_BOARDS_FEX_FILE to a sensible value in the autobuilder
> scripts?

Ok, will do that. Will you also do the same on your autobuilders? I
really should clean up my script, and share it so that we can try to
run the same logic.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-05 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 16:21 [Buildroot] [PATCH 1/2] linux: qstrip the custom DTS path Thomas Petazzoni
2013-06-05 16:21 ` [Buildroot] [PATCH 2/2] sunxi-boards: set a default board Thomas Petazzoni
2013-06-05 19:14   ` Peter Korsgaard
2013-06-05 19:38     ` Thomas Petazzoni [this message]
2013-06-05 19:45       ` Peter Korsgaard
2013-06-05 20:26         ` Thomas Petazzoni
2013-06-05 20:33           ` Peter Korsgaard
2013-06-05 19:05 ` [Buildroot] [PATCH 1/2] linux: qstrip the custom DTS path Peter Korsgaard

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=20130605213807.0c015c5d@skate \
    --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.