path: root/recipes-connectivity/consul
AgeCommit message (Collapse)Author
2022-03-25consul: add https to github SRC_URIBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2021-11-02global: convert github SRC_URIs to use https protocolBruce Ashfield
github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2021-10-29global: add explicit branch to all SRC_URIsmaster-nextBruce Ashfield
As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2021-07-31global: overrides conversionBruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2021-07-23consul: add explicit branch specificationBruce Ashfield
Consul has switched from master to main for development, we add an explicit branch statement, since the default of master no longer works. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2021-03-16consul: export GO111MODULE=offChen Qi
With the latest go version bump in oe-core export GO111MODULE is on by default. Our build is not setup to use go modules, so we disable it and avoid configuration errors. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-12-01consul: fix compile failure while go upgraded to 1.13hongxu
While go was upgraded to 1.13, there is a do_compile failure, Refer upstream envoyproxy to rename imports throughout https://github.com/envoyproxy/protoc-gen-validate/pull/161/commits/7428b5f8e7fdabbcc7c9710e23e6f438ba4ff021 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-09-09consul: Not automatically start system service on bootHe Zhe
The systemd service needs to be tuned according to various use cases and cannot be able to always start successfully for example when there is no network interface named br0 by default. Thus the default configuration is mainly used as an example. Let's not automatically start it on boot. Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-09-09consul: Upgrade to 1.6.0He Zhe
1.6.0 is the latest release. Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-04-07consul: don't build with the '-linkshared' optionMark Asselstine
We are currently seeing the following error: type..eUfRrckI: missing section for relocation target type..FEeY9FdU ... This is similar to the reported issues http://www.lyddzz.com/github_/golang/go/issues/30768 and https://github.com/hashicorp/consul/issues/5486 (but this one appears to be a report of 'our' issue so isn't really valid) The go.bbclass currently completes 2 builds (if GO_DYNLINK is set), one without '-linkshared' and one with. The '--linkshared' option is marked as experimental (https://golang.org/cmd/link/ -- "-linkshared Link against installed Go shared libraries (experimental)"). By setting GO_LINKSHARED prior to inheriting go.bbclass we can overwrite the default compile behavior and only perform the build without the '-linkshared' option. This shouldn't change the functionality of consul and we can revert to the default behavior when the issues have been addressed. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-03-08consul: uprev to v1.4.3Hongzhi.Song
Uprev to v1.4.3 and remove invalid patch. Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-02-21consul: do not try to build for mipsJoe Slater
Use COMPATIBLE_HOST to prevent building for mipsarch. Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2018-10-11consul: add INSANE_SKIP for textrelChangqing Li
1. for i586, bitbake consul will have QA error of textrel. consul-git-r0 do_package_qa: QA Issue: ELF binary i 'work/i586-wrs-linux/consul/git-r0/packages-split/consul/usr/bin/consul' has relocations in .text [textrel] according to go doc: -buildmode=pie Build the listed main packages and everything they import into position independent executables (PIE). Packages not named main are ignored. checked use command "eu-findtextrel ./consul", functions not compiled with -fpic/-fPIC are from packages not named main, and also not imported into package main. so -buildmode=pie cannot reslove this problem. so refer commit b689c72a of oe-core, just skip it. 2. This problem is caused since security_flags.inc is used by default. so alternative work around is: SECURITY_CFLAGS_pn-consul = "${SECURITY_NOPIE_CFLAGS}" SECURITY_LDFLAGS_pn-consul = "" Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-25consul-migrate: update to use go.bbclassMark Asselstine
We do not want meta-cloud-services to depend on meta-overc so we switch to use the go.bbclass which is now part of oe-core/yocto. We also capture all the licenses for all source packages which are included in consul-migrate and adjust paths to account for the different handling of go.bbclass vs. golang.bbclass. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-25consul-migrate: use SRC_URIs not DEPENDSMark Asselstine
It is common to have two GO packages, A and B, and they both depend on a GO dependency, C. This can be satisfied using the current technique of writing recipes for each dependency. BUT it is also common for GO packages to not only specify other packages in their GoDeps but also specific dependency versions. In the case that A and B share a dependency on C, but require different versions, there is no easy way to accomplish this using recipes. Since GO dependencies are also source dependencies and these dependencies are overwhelmingly useless on their own, writing recipes for each is overkill. We therefor replace DEPENDS with SRC_URIs and SRCREVs as a mechanism to provide build dependencies. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-25consul: update to use go.bbclassMark Asselstine
We don't want meta-cloud-services to have to rely on meta-overc for access to golang.bbclass (which predates go.bbclass in oe-core/yocto) so switch to make use of go.bbclass. This requires the definition of GO_IMPORT and the dropping of some custom handling of 'configure' and others. Since go.bbclass uses a slighly different directory structure than we used with golang.bbclass we have to adjust some paths accordingly, including those in patches. We also need to expand the list of LICENSES to cover licenses of all the GO packages included in consul. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-25consul: remove unneeded DEPENDSMark Asselstine
GO package dependencies are a tricky beast. They are source dependencies and if you have two packages which share a dependency they could very well require different versions of the dependency. So supplying the dependencies via bitbake recipes is not an easy proposition. As such we are better off populating the build source with the dependencies using SRC_URIs and not traditional DEPENDS. That being said, the consul source repository actually includes copies of the dependencies (and the dependency's dependencies) so having these DEPENDS is actually useless and we can simply drop them. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2018-09-25consul: consule-migrate: move from meta-overcMark Asselstine
After several requests to make the consul recipe available outside of meta-overc and the OverC framework we are moving the consul recipes here. These are a copy from meta-overc (HEAD 6afe8d2c12ac). NOTE that not all the DEPENDS have been copied as we will follow this commit with work to make use of SRC_URIs for dependencies. See the associated commit(s) which will follow this one. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>