From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/3] docker-containerd: new package
Date: Fri, 27 May 2016 21:49:22 +0200 [thread overview]
Message-ID: <20160527214922.581fa744@free-electrons.com> (raw)
In-Reply-To: <CA+h8R2pT_U2JUKbW-y+y5mHrCGM08=Qq7mA2SgU9Kpk-zTLJcA@mail.gmail.com>
Hello,
On Fri, 27 May 2016 00:02:55 -0700, Christian Stewart wrote:
> > + depends on BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
> >
>
> > BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS dependency.
> >
>
> Not sure what you're saying here
I explained it in the review of another patch from you.
When you have:
comment "<foo> needs a toolchain w/ threads"
depends on !BR2_TOOLCHAIN_HAS_THREADS
you *must* also add:
depends on BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
so that the comment doesn't show up on architectures for which there is
no Go support.
Otherwise, imagine a user creating a configuration for say the Blackfin
architecture (which doesn't have Go support), and initially with thread
disabled. They see the comment "<foo> needs a toolchain w/ threads". So
the user goes in the Toolchain menu, and enables thread. And then, the
comment has disappeared, but the option to enable the package has not
appeared.
Hence, we want to show the comment only when
BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS=y.
> In terms of all the versioning stuff. I'll try using the _VERSION variables
> for this. As the variable specifically references a GitCommit, I included
> the commits as it wants. But it's probably not too bad of a compromise to
> use the version ID as the commit hash.
If it works, it's much better.
> For the host variable, a patch series recently applied changed what that
> variable contained, and in particular, the changes to CGO caused the build
> to completely fail unless I included the variables from there, so I now
> include it and simply add a few things on top of it to build the full build
> env for the package.
>
> Will revise on all of the series and respin late tomorrow, in case anyone
> else has suggestions :)
ACK, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-27 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 4:52 [Buildroot] [PATCH v4 0/3] Add docker engine support Christian Stewart
2016-05-27 4:52 ` [Buildroot] [PATCH v4 1/3] runc: new package Christian Stewart
2016-05-27 5:25 ` Thomas Petazzoni
2016-05-27 4:52 ` [Buildroot] [PATCH v4 2/3] docker-containerd: " Christian Stewart
2016-05-27 5:27 ` Thomas Petazzoni
2016-05-27 7:02 ` Christian Stewart
2016-05-27 19:49 ` Thomas Petazzoni [this message]
2016-05-27 4:52 ` [Buildroot] [PATCH v4 3/3] docker-engine: " Christian Stewart
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=20160527214922.581fa744@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox