From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] sunxi-boards: set a default board
Date: Wed, 05 Jun 2013 21:45:25 +0200 [thread overview]
Message-ID: <878v2ocpey.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130605213807.0c015c5d@skate> (Thomas Petazzoni's message of "Wed, 5 Jun 2013 21:38:07 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>> Hmm, how is this different that what we do for the barebox/u-boot/linux
>> configurations?
Thomas> It is different in that this package starts with BR2_PACKAGE,
Thomas> so it can get selected by the randpackageconfig logic, while
Thomas> barebox/u-boot/linux Kconfig options don't start by
Thomas> BR2_PACKAGE, so they don't get selected by randpackageconfig :)
True, but we have the same problem with E.G. BR2_PACKAG
E_QT_LICENSE_APPROVED / BR2_PACKAGE_QT5BASE_LICENSE_APPROVED. If these
are not set the build will also get stuck, so we preseed them in the
autobuilders (I do atleast).
>> 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?
Thomas> Ok, will do that. Will you also do the same on your
Thomas> autobuilders? I really should clean up my script, and share it
Thomas> so that we can try to run the same logic.
Yes, I'll fixup "mine" as well.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-06-05 19:45 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
2013-06-05 19:45 ` Peter Korsgaard [this message]
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=878v2ocpey.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox