From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14631] New: host-go-bootstrap: go not being built for package in external tree
Date: Tue, 01 Mar 2022 19:49:59 +0000 [thread overview]
Message-ID: <bug-14631-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14631
Bug ID: 14631
Summary: host-go-bootstrap: go not being built for package in
external tree
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: contact@martb.dev
CC: buildroot@uclibc.org
Target Milestone: ---
Hey,
running on 2022.02-rc2.
I tried adding a local go package inside my external tree using the following
stripped down config.
Config.in (included correctly, showing up inside menuconfig)
```
config BR2_PACKAGE_APOGEE
bool "apogee"
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
help
my help string
```
.mk
```
APOGEE_SITE = $(BR2_EXTERNAL_MYTREE_PATH)/src/apogee
APOGEE_SITE_METHOD = local
APOGEE_BUILD_TARGETS = cmd/apogee
APOGEE_INSTALL_BINS = apogee
APOGEE_GOMOD = "<stripped>/apogee"
...
$(eval $(golang-package))
```
Whenever i try building this package i get:
```
/bin/sh: Line 1:
/home/<censored>/Schreibtisch/<censored>/mytree/output/host/bin/go: File or
directory not found
```
Building a different go package like tinifier seems to trigger the bootstrap
build fine though.
Is this some limitation due to the "local" site source or due to the external
tree im using?
Kind regards
Martin
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-03-01 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 19:49 bugzilla [this message]
2022-03-06 15:33 ` [Buildroot] [Bug 14631] host-go-bootstrap: go not being built for package in external tree bugzilla
2022-03-07 19:02 ` bugzilla
2022-03-07 21:29 ` bugzilla
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=bug-14631-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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