summaryrefslogtreecommitdiffstats
path: root/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* python3-websocket-client: make py2 version availableMark Asselstine2017-12-283-11/+15
| | | | | | | | Allow a py2 version of the python-websocket-client package to be built. This is required to support updates in meta-cloud-services. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-dockerpty: fix license-checksum qa issueAbdur Rehman2017-11-151-1/+1
| | | | | | | Fix license path and checksum for python3-dockerpty. Signed-off-by: Abdur Rehman <abdur_rehman@mentor.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-*: switch remaining pypi recipes to use the pypi classMark Asselstine2017-11-153-19/+8
| | | | | | | | | | | | | | Cleanup the various python-* recipes which download from pypi. The biggest change is to "inherit pypi" which should result in us always using current pypi best practices. This will for example ensure we are using https and not http which is apparently going to be disabled soon. Where the default behavior in the pypi class wasn't sufficient we make use of the PYPI_* variables to overwrite the defaults. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-webob: uprev to v1.7.3Mark Asselstine2017-11-072-23/+18
| | | | | | | | | | The only user in meta-virtualization is python-bugsnag and there is no version dependency. This new version is however required by the latest openstack. Switched to using the "common" pypi.bbclass while we are at it. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-docker: add missing RDEPENDSRicardo Salveti2017-10-171-0/+6
| | | | | | | | | Add python3-docker-pycreds, python3-requests and python3-websocket-client to RDEPENDS for a functional python docker module (otherwise even import docker fails). Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-docker-compose: add version 1.16.1 + dependenciesPascal Bach2017-09-159-0/+78
| | | | | | | | | This requires some packages as well as the pypi.bbclass from meta-python. It uses Python 3 as I don't think it makes sense to use Python 2 anymore. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-systemd: Fix QA dependency problemJason Wessel2017-08-221-3/+1
| | | | | | | | | | | | | ERROR: go-systemd-4+gitb4a58d95188dd092ae20072bac14cece0e67c388-r0 do_package_qa: QA Issue: /usr/local/go/src/github.com/coreos/go-systemd/test contained in package go-systemd requires /bin/bash, but no providers found in RDEPENDS_go-systemd? [file-rdeps] Resolved with proper dependency to bash. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-itsdangerous: Drop recipeAdrian Dudau2017-08-141-22/+0
| | | | | | | | Same version of the recipe is maintained in meta-python, no need to keep a duplicate here. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-simplejson: Drop recipeAdrian Dudau2017-08-141-31/+0
| | | | | | | | | Newer version of the recipe (v3.11.1) is already maintained in meta-python and I couldn't find any hard dependencies on the current version. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-six: Drop recipeAdrian Dudau2017-08-031-19/+0
| | | | | | | Same recipe is maintained in oe-core, no need to keep a duplicate here. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-requests: Drop recipeAdrian Dudau2017-07-101-28/+0
| | | | | | | | | There's a newer recipe (v2.13) maintained in meta-python. meta-openstack explicitly prefers that version over this one, so no point in keeping this recipe since nobody else is using this version. Signed-off-by: Adrian Dudau <adrian.dudau@enea.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* devtools: remove protobuf*Bruce Ashfield2017-06-276-234/+0
| | | | | | | | | | The protobuf recipes are in meta-oe, and were only here to support higher order virtualization tasks. Dropping the recipes and we'll use the ones directly from meta-oe, since the versions and compatibility should be fine. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python3-twisted: temporarily add recipeMark Asselstine2017-06-222-0/+311
| | | | | | | | | This will eventually be available in meta-openembedded so will be able to be reverted. This will allow us to use openvswitch with python3 in the interim. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf-native: Drop PR = 0Khem Raj2017-03-211-2/+0
| | | | | | | Drop PR setting to 0 its default anyway Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf-native: Enable shared libsKhem Raj2017-03-211-1/+1
| | | | | | | | protobuf-c needs shared libraries, linking with static libs ends up with undefined symbols Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* tools: remove go from meta-virtualizationBruce Ashfield2017-03-2024-936/+0
| | | | | | go is now part of oe-core, so we can drop the meta-virt local recipes. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker: fixup failing buildMark Asselstine2017-02-0912-17/+190
| | | | | | | | | | | | | | Docker is failing to build because it is attempting to download missing go dependencies. Add new recipes for missing dependencies and update existing recipes to ensure the version defined in docker's vendor.conf is available. Note that this fixes the build only. At this time many docker functions are working, such as 'docker image', 'docker pull' and more, but 'docker run' is currently failing. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: add ${TARGET_ARCH} to PNMark Asselstine2017-02-091-0/+3
| | | | | | | | | | | | Since we are building a cross tool which produces something which is ARCH specific we should stick to the <toolname>-cross-<arch> naming convention. A variant of this patch has been floating around for a while but with the changes around per recipe sysroots, distributed builds, shared builds... we are best served to adopt this convention now. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-native: rename to go-initial-nativeMark Asselstine2017-02-092-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | With the new per recipe sysroots we were having build issues since the bootstrap version of go (go-native 1.4) was being found and not the go-cross (1.6) we are expecting. This results in errors such as the following when building packages such as containerd: _cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 This is caused by the dependency tree built up to prepare the per recipe sysroot. Since recipes like containerd DEPEND on go-cross and go-cross DEPENDS on go-native both are installed but unlike the old global sysroot the dependency parsing order results in go-native being last, overwriting go-cross. You can see this by running a devshell for containerd and running 'go version'. By adding '-initial' in the name we exploit functionality in sstate.bbclass that is already in place to handle gcc-initial and similar. This results in only explicit DEPENDS on go-native being enforced, so in the case of containerd we only get a dependency on go-cross and we therefor get go 1.6 as expected. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: depend on virtual/${TARGET_PREFIX}gccMark Asselstine2017-02-011-1/+1
| | | | | | | | | | | | | This fixes the compile time error #runtime/cgo exec: "x86_64-overc-linux-gcc": executable file not found in $PATH Since we set CC_FOR_TARGET to ${TARGET_PREFIX}gcc we need to ensure this is present by adding it to the recipe DEPENDS. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-sqlalchemy: uprev to latest in 1.0.x seriesMark Asselstine2017-01-201-4/+4
| | | | | | | | | | | | | | According to the changelog at (http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html) this is mostly bug fixes. We need a version >= 1.0.10 to properly support the python-oslo.db uprev to stable/newton in meta-cloud-services. NOTE the license checksum has changed do to content change, not because the package license has changed, it is still MIT. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-sqlalchemy: Add 1.1.5Huang Qiyu2017-01-201-0/+16
| | | | | | | | | 1) Copy the v1.0.9 bb to create python-sqlalchemy v1.1.5. 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-sqlalchemy: 1.0.8 -> 1.0.9Huang Qiyu2017-01-171-2/+2
| | | | | | | Upgrade python-sqlalchemy from 1.0.8 to 1.0.9. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-sphinx: 1.3.1 -> 1.4.1Huang Qiyu2017-01-141-3/+3
| | | | | | | | 1) Upgrade python-sphinx from 1.3.1 to 1.4.1 2) License checksum changed,since the copyright years were updated. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-webob 1.4.1 -> 1.6.0Huang Qiyu2017-01-141-2/+2
| | | | | | | Upgrade python-webob from 1.4.1 to 1.6.0. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* openvswitch: fix build host contaminationMark Asselstine2017-01-141-0/+2
| | | | | | | | | | | | | | | | | | | | | | There is only a single PYTHON variable for configure and yet python is used for the build as well as scripts installed on the target. If we set a path in PYTHON as we had we end up using this same path during the build and since it isn't to the sysroot we end up with host contamination (as demonstrated by python failing to import 'six' on build hosts without python-six installed. The best approach is to set PYTHON to "python" when calling configure, ie. without a path. This will use 'python' from the path during build time and by ensuring all the installed scripts use '/usr/bin/env' we can ensure python will be found on the target when the scripts are run. Since 'six' is used as part of the build we have to ensure it is -native'ly buildable and we set all the required build and runtime dependencies. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Remove True option to getVar callsPaul Barker2017-01-031-1/+1
| | | | | | | getVar() now defaults to expanding by default. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: uprev 3.1.0 from 3.0.0Wenzong Fan2016-11-222-6/+6
| | | | | Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: ptest: Fix QA file-rdep warningHe Zhe2016-10-211-0/+1
| | | | | | | | | | | Add bash to ptest's RDEPENDS "WARNING: QA Issue: /usr/lib64/protobuf/ptest/run-ptest_protobuf-ptest contained in package protobuf-ptest requires /bin/bash, but no providers found in its RDEPENDS [file-rdeps]" Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: Fix QA error for GNU_HASHHe Zhe2016-10-211-1/+1
| | | | | | | | | | | Add LDFLAGS to examples makefile to pass default ld flags. "ERROR: protobuf-3.0.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '.../protobuf/3.0.0-r0/packages-split/protobuf-ptest/usr/ lib/protobuf/ptest/add_person_cpp'" Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: Fix failure if building go-cross firstJason Wessel2016-10-191-1/+2
| | | | | | | | If go-cross is built as the first package it will fail creating the target libraries used for cross-compilation because it requires libgcc. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-native: Add work around for binutils >= 2.27Jason Wessel2016-10-191-1/+1
| | | | | | | | | | | | | | | We only use go-native to bootstrap go-cross and according to a post in the go-lang git it is possible to work around by disabling CGO: https://github.com/golang/go/issues/16906 This patch fixes the compile failure with binutils 2.27 which has the message: cannot load DWARF output from $WORK/net/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: Fix host contamination for x86_64 host to x86_64 targetJason Wessel2016-10-121-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | The go-cross package is explicitly for compiling target libraries on the host system. When the target architecture matches the host architecture it will actually use the host's linker and compiler however which can result in the generation of the cgo.a library having linker symbols which might not work properly when compiling other packages. A typical error looks like this when building consul-migrate: /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/lib/x86_64-linux/go/pkg/tool/linux_amd64/link: running x86_64-yocto-linux-gcc failed: exit status 1 /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: /opt/build-intel-x86/tmp/work/core2-64-yocto-linux/consul-migrate/git-r0/build-tmp/go-link-956548052/000002.o: unrecognized relocation (0x2a) in section `.text' /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: final link failed: Bad value collect2: error: ld returned 1 exit status The fix is to use the make.bash --target-only option to properly build the libraries with the target toolchain. The "go" binaries are thrown away but the cross compilation libraries are preserved. The sysroot strip also has to be disabled because it will run the host strip on the target binaries. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Revert "go-cross: Fix host contamination for x86_64 host to x86_64 target"Bruce Ashfield2016-09-231-9/+1
| | | | | | | | | | | | | | | | | | | | | | | This is breaking the build of go-cross on some machines: Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 20 static | ERROR: oe_runmake failed | /home/bruce/poky/build/tmp/work/core2-64-poky-linux/containerd/0.2.2+git0ac3cd1be170d180b2baed755e8f0da547ceb267-r0/git | cd ctr && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/ctr | cd containerd && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/containerd | cd containerd-shim && go build -ldflags "-w -extldflags -static -X github.com/docker/containerd.GitCommit=0ac3cd1be170d180b2baed755e8f0da547ceb267 " -tags "" -o ../bin/containerd-shim | # github.com/docker/docker/pkg/term | cannot load DWARF output from $WORK/github.com/docker/docker/pkg/term/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 | make: *** [shim-static] Error 2 | make: *** Waiting for unfinished jobs.... | # github.com/docker/docker/pkg/term | cannot load DWARF output from $WORK/github.com/docker/docker/pkg/term/_obj//_cgo_.o: decoding dwarf section info at offset 0x4: unsupported version 0 | # github.com/opencontainers/runc/libcontainer/system | cannot load DWARF output from $WORK/github.com/opencontainers/runc/libcontainer/system/_obj//_cgo_ This reverts commit 7ff08e542d15b8e0104185768debf360044af7d1.
* go-cross: Fix host contamination for x86_64 host to x86_64 targetJason Wessel2016-09-221-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | The go-cross package is explicitly for compiling target libraries on the host system. When the target architecture matches the host architecture it will actually use the host's linker and compiler however which can result in the generation of the cgo.a library having linker symbols which might not work properly when compiling other packages. A typical error looks like this when building consul-migrate: /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/lib/x86_64-linux/go/pkg/tool/linux_amd64/link: running x86_64-yocto-linux-gcc failed: exit status 1 /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: /opt/build-intel-x86/tmp/work/core2-64-yocto-linux/consul-migrate/git-r0/build-tmp/go-link-956548052/000002.o: unrecognized relocation (0x2a) in section `.text' /opt/build-intel-x86/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-yocto-linux/gcc/x86_64-yocto-linux/5.2.0/ld: final link failed: Bad value collect2: error: ld returned 1 exit status The fix is to use the make.bash --target-only option to properly build the libraries with the target toolchain. When the host architecture does not match the target architecture we must also force build the target libraries or they get dynamically populated into the sysroot in an uncontrolled manner by the first package that uses go-cross to compile code. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf-c: uprev to 1.2.1 from 0.15Jianchuan Wang2016-09-122-20/+28
| | | | | Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: uprev 3.0.0 from 2.6.1Jianchuan Wang2016-09-122-15/+18
| | | | | Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-distribution-digest: Fix do_package failureJason Wessel2016-09-071-5/+3
| | | | | | | | | | | | | | | | | | | | The rule in the recipe which deletes all but LICENSE and the digest directory is broken depending on what ascii table bash uses by default for matching, specifically: rm -rf ${S}/[A-KM-Za-ce-z]* ${S}/doc* The "A-K" piece will actually match both upper and lower case when the acsii because the ascii value is checked as being between two numbers: 0x41=a, 0x42=A,0x43=b...0x48=D This is contray to what you would typically think should work with the lower and uppers separated into two contiguous spaces. To fix this, instead of using the "rm" logic, we can copy the components we need instead. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: fix source locationVenkateswara Rao Mandela2016-09-063-12/+11
| | | | | | | | | | | The file locations listed in the recipes for protobuf, protobuf-c are not currently available. Updating the recipe to 1. Point URI's to valid locations. 2. Update checksums and increment version numbers. Signed-off-by: Venkateswara Rao Mandela <venkat.mandela@ti.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: allow tmp directory to already existBruce Ashfield2016-05-252-2/+2
| | | | | | | | | | | | | | | The change [go-native: don't use host /var/tmp for temp build artifacts] fixed builds, but it is possible that the tmp directory already exists, which results in the following failure: | DEBUG: Executing shell function do_compile | mkdir: cannot create directory 'tmp/work/x86_64-linux/go-cross/1.6.2-r0/build-tmp': File exists | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at tmp/work/x86_64-linux/go-cross/1.6.2-r0/temp/log.do_compile.29142) By adding a -p to the mkdir calls, we can survive this scenario. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: Add RDEPENDS for ptestHe Zhe2016-05-251-0/+1
| | | | | | | | | | | This patch adds bash and python to ptest's RDEPENDS to avoid the following warning: "WARNING: QA Issue: /usr/lib64/protobuf/ptest/run-ptest_protobuf-ptest contained in package protobuf-ptest requires /bin/bash, but no providers found in its RDEPENDS [file-rdeps]" Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* protobuf: add protobuf-2.5.0 into devtoolZumeng Chen2016-05-206-0/+224
| | | | | | | | | Protocol Buffers(a.k.a., protobuf) are language-neutral, platform-neutral, extensible mechanism for serializing structured data, so it is reasonable to be a part of development tool recipe. Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-native: don't use host /var/tmp for temp build artifactsMark Asselstine2016-05-201-0/+4
| | | | | | | | | | | | | | | | Similar to a recent change for go-cross we can potentially run in to a build failure: go tool dist: mkdtemp(/var/tmp/go-cbuild-A0rrP5): No such file or directory when the host doesn't have a /var/tmp or when the permissions don't allow for the creation of the temporary directory. Instead of relying on /var/tmp we create and use a temporary directory in the $WORKDIR to work around this issue. This is passed to the build via the TMPDIR environment variable. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* docker: drop obselete dependenciesBruce Ashfield2016-05-182-62/+0
| | | | | | | | | | | We no longer need go-net and go-sqlite for the docker build and runtime. The upstream repos are no longer properly fetching, so we can simply drop the recipes and dependency. If they are ever needed in the future, we can revisit the upstream source for them. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: don't use host /var/tmp for temporary build artifactsMark Asselstine2016-05-161-1/+5
| | | | | | | | | | | | | | | | The default behavior for go-cross build is to use the path specified in TMPDIR for some temporary build artifacts and if no TMPDIR is set in the environment to fallback to use /var/tmp. This causes a build failure on hosts that do not have a /var/tmp or that have restrictive permissions on /var/tmp. The failure is seen as: go tool dist: mkdtemp(/var/tmp/go-cbuild-yhmNbi): No such file or directory By setting TMPDIR and ensuring we create this directory we can avoid the associated issue with using the default. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go: add go-cross 1.6Bruce Ashfield2016-05-028-0/+240
| | | | | | | Introduce the 1.6 go release, and port patches to apply to this version. Existing versions (1.5) are not removed, so this is not a forced update. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: add relocation fix to 1.4 for new binutils.Paul Gortmaker2016-04-222-0/+224
| | | | | | | | | | | | | | | | | | | | | | | Add relocation fix as documented in contained commit log, so that we can build with newer binutils, as per the ones we get via the self hosted builder and things like build-appliance. Fixes: | go-native/1.4.3-r0/go/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown relocation type 42; compiled without -fpic? | go-native/1.4.3-r0/go/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown relocation type 42; compiled without -fpic? | runtime/cgo(.text): unexpected relocation type 298 | runtime/cgo(.text): unexpected relocation type 298 | # cmd/go | go-native/1.4.3-r0/go/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown relocation type 42; compiled without -fpic? | go-native/1.4.3-r0/go/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown relocation type 42; compiled without -fpic? | runtime/cgo(.text): unexpected relocation type 298 | runtime/cgo(.text): unexpected relocation type 298 | WARNING: go-native/1.4.3-r0/temp/run.do_compile.30243:1 exit 2 from './make.bash --host-only' | ERROR: Function failed: do_compile (log file is located at go-native/1.4.3-r0/temp/log.do_compile.30243) ERROR: Task 6 (meta-virtualization/recipes-devtools/go-cross/go-native_1.4.bb, do_compile) failed with exit code '1' Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
* go-cross: uprev 1.4.2 --> 1.4.3Paul Gortmaker2016-04-221-3/+3
| | | | | | | There is a fix for newer binutils that was aimed at being placed on the 1.4.3 baseline, so update accordingly. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
* go-cross: uprev to 1.5.2Zongchun Yu2016-04-1919-286/+449
| | | | | | | | * Add go-native as build bootstrap for go-cross. * Upgrade go-cross to v1.5.2 Signed-off-by: Zongchun Yu <zongchun.yu@nxp.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* python-m2crypto: Fix issue with swig 3.0.5Jackie Huang2016-04-052-1/+161
| | | | | | | | | | | | | The version 0.22.3 of python-m2crypto fails to work after swig updated to 3.0.5+: AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN' It's fixed since 0.22.4 and we could update it to latest version, but docker-registry depends on the version 0.22.3, so backport the patch to fix the issue with swig 3.0.5. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-26 05:59:36 +0000