From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package: hide golang packages for toolchains with binutils bug 20006
Date: Sat, 24 Nov 2018 22:56:01 +0100 [thread overview]
Message-ID: <20181124225601.4e592936@windsurf> (raw)
In-Reply-To: <3eaf225466a426cf89218531a5c9d685c2224a18.1543096295.git.yann.morin.1998@free.fr>
Hello,
On Sat, 24 Nov 2018 22:52:01 +0100, Yann E. MORIN wrote:
> Fixes:
> http://autobuild.buildroot.org/results/020/02039969b16534d4020ecd4574bae71b91c1e6b8/ (flannel)
> http://autobuild.buildroot.org/results/e95/e9528b06b350ef84c1e2cb59fba87b4db77b4660/ (docker-engine)
> [...]
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: Romain Naour <romain.naour@gmail.com>
> ---
> package/docker-containerd/Config.in | 4 ++++
> package/docker-engine/Config.in | 4 ++++
> package/docker-proxy/Config.in | 4 ++++
> package/flannel/Config.in | 4 ++++
> package/mender/Config.in | 4 ++++
> package/runc/Config.in | 4 ++++
> 6 files changed, 24 insertions(+)
>
> diff --git a/package/docker-containerd/Config.in b/package/docker-containerd/Config.in
> index 851345f73e..39f6ea8ee8 100644
> --- a/package/docker-containerd/Config.in
> +++ b/package/docker-containerd/Config.in
> @@ -4,6 +4,7 @@ config BR2_PACKAGE_DOCKER_CONTAINERD
> depends on BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS
> depends on BR2_TOOLCHAIN_HAS_THREADS
> depends on BR2_USE_MMU # util-linux
> + depends on !BR2_TOOLCHAIN_HAS_BINUTILS_BUG_20006
> select BR2_PACKAGE_RUNC # runtime dependency
> select BR2_PACKAGE_UTIL_LINUX # runtime dependency
> select BR2_PACKAGE_UTIL_LINUX_BINARIES
> @@ -32,3 +33,6 @@ comment "docker-containerd needs a toolchain w/ threads"
> depends on BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS
> depends on BR2_USE_MMU
> depends on !BR2_TOOLCHAIN_HAS_THREADS
> +
> +comment "docker-containerd needs a toolchain not affected by binutils bug 20006"
> + depends on BR2_TOOLCHAIN_HAS_BINUTILS_BUG_20006
This comment should not appear on architecture not supported by go, so
you should replicate at least:
depends on BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
depends on BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS
However, overall, I'm wondering if we shouldn't keep it simple and
stupid, and simply make BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS depend on
BR2_TOOLCHAIN_HAS_BINUTILS_BUG_20006. Yes, there won't be comments in
each and every package, but do we really need that for such a corner
case ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-24 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 21:51 [Buildroot] [PATCH 0/3] golang: fix build with oldisj codesourcery amd64 toolchain Yann E. MORIN
2018-11-24 21:51 ` [Buildroot] [PATCH 1/3] infra/pkg-golang: enforce number of parallel jobs Yann E. MORIN
2018-11-24 21:52 ` [Buildroot] [PATCH 2/3] toolchain: CodeSourcery AMD64 affected by PR20006 Yann E. MORIN
2018-11-24 21:52 ` [Buildroot] [PATCH 3/3] package: hide golang packages for toolchains with binutils bug 20006 Yann E. MORIN
2018-11-24 21:56 ` Thomas Petazzoni [this message]
2018-11-25 8:48 ` Yann E. MORIN
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=20181124225601.4e592936@windsurf \
--to=thomas.petazzoni@bootlin.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