Bug 14631 - host-go-bootstrap: go not being built for package in external tree
Summary: host-go-bootstrap: go not being built for package in external tree
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-01 19:49 UTC by Martin Böh
Modified: 2022-03-07 21:29 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Böh 2022-03-01 19:49:59 UTC
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
Comment 1 Fabrice Fontaine 2022-03-06 15:33:04 UTC
Hello,

Thanks for your bug report, the following patch should fix your issue:
https://patchwork.ozlabs.org/project/buildroot/patch/11477_1644506977_62052F61_11477_142_1_1cfdf4aa3ac96d2d2cf246385325f93b451d773b.1644506959.git.yann.morin@orange.com/

Unfortunately, this patch has not been applied to master yet.

Best Regards,

Fabrice
Comment 2 Martin Böh 2022-03-07 19:02:10 UTC
Thanks for bringing this to my attention Fabrice!

Applied for now, i hope it makes its way into 2022.02 sooner or later.