From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] package/delve: new package
Date: Sat, 2 Jan 2021 18:30:26 +0100 [thread overview]
Message-ID: <20210102183026.0de43d73@windsurf> (raw)
In-Reply-To: <20201216080013.547261-6-christian@paral.in>
Hello Christian,
On Wed, 16 Dec 2020 00:00:13 -0800
Christian Stewart <christian@paral.in> wrote:
> Delve is a debugger for the Go programming language.
>
> Signed-off-by: Christian Stewart <christian@paral.in>
I have applied, but after doing some changes. See below.
> diff --git a/package/delve/Config.in b/package/delve/Config.in
> new file mode 100644
> index 0000000000..008f00d789
> --- /dev/null
> +++ b/package/delve/Config.in
> @@ -0,0 +1,18 @@
> +config BR2_PACKAGE_DELVE
> + bool "delve"
> + depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
> + depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + depends on BR2_TOOLCHAIN_USES_GLIBC # go, cgo
> + depends on !BR2_TOOLCHAIN_USES_UCLIBC # go
There is no such dependency on glibc && !uclibc in Go.
> + depends on BR2_USE_MMU # go
There is no dependency on BR2_USE_MMU in Go.
So both of these do not make sense. However, delve has indeed a limited
set of CPU architectures it supports. Apparently, just aarch64, i386
and x86-64, according to pkg/proc/native/support_sentinel.go in the
code base.
So I've replaced the Config.in file with this:
# Supported architectures are listed in
# pkg/proc/native/support_sentinel.go
config BR2_PACKAGE_DELVE_ARCH_SUPPORTS
bool
default y if BR2_aarch64
default y if BR2_i386
default y if BR2_x86_64
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
config BR2_PACKAGE_DELVE
bool "delve"
depends on BR2_PACKAGE_DELVE_ARCH_SUPPORTS
depends on BR2_TOOLCHAIN_HAS_THREADS
help
Delve is a debugger for the Go programming language.
https://github.com/go-delve/delve
comment "delve needs a toolchain w/ threads"
depends on BR2_PACKAGE_DELVE_ARCH_SUPPORTS
depends on !BR2_TOOLCHAIN_HAS_THREADS
I have verified that it builds fine on uClibc/i386 and musl/aarch64 for
example, which confirms that the glibc && !uclibc dependency was not
correct.
Applied with this fixed. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-02 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 8:00 [Buildroot] [PATCH 1/5] package/docker-containerd: fix version output ldflags Christian Stewart
2020-12-16 8:00 ` [Buildroot] [PATCH 2/5] package/runc: " Christian Stewart
2020-12-30 8:28 ` Thomas Petazzoni
2021-01-05 16:35 ` Peter Korsgaard
2020-12-16 8:00 ` [Buildroot] [PATCH 3/5] package/docker-containerd: specify correct build targets Christian Stewart
2020-12-30 8:32 ` Thomas Petazzoni
2020-12-16 8:00 ` [Buildroot] [PATCH 4/5] package/docker-cli: bump version to 20.10.1 Christian Stewart
2020-12-30 8:37 ` Thomas Petazzoni
2020-12-16 8:00 ` [Buildroot] [PATCH 5/5] package/docker-engine: " Christian Stewart
2020-12-17 6:01 ` Tian Yuanhao
2020-12-30 8:37 ` Thomas Petazzoni
2020-12-16 8:00 ` [Buildroot] [PATCH v1 1/1] package/delve: new package Christian Stewart
2020-12-16 18:07 ` Peter Seiderer
2021-01-02 17:30 ` Thomas Petazzoni [this message]
2020-12-30 8:28 ` [Buildroot] [PATCH 1/5] package/docker-containerd: fix version output ldflags Thomas Petazzoni
2021-01-05 16:31 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 7:27 [Buildroot] [PATCH v1 1/1] package/delve: new package 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=20210102183026.0de43d73@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 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.