linux/meta-virtualization.git/recipes-devtools, branch morty

go-fsnotify: switch to new repository on github

2018-03-23T21:11:40+00:00

fsnotify is changed to new repository on gihub, so adapt this chanage accordingly to avoid fetch failure. Signed-off-by: Yunguo Wei Signed-off-by: Bruce Ashfield

python-*: use https for pypi URLs

2017-12-02T02:50:47+00:00

Several of the recipes here were using http URLs for source hosted on pypi - pypi apparently no longer supports http so switch to https instead. Apply this commit [1] to morty branch. [1] https://www.mail-archive.com/meta-virtualization@yoctoproject.org/msg02821.html Signed-off-by: Fabio Berton Signed-off-by: Bruce Ashfield

protobuf: ptest: Fix QA file-rdep warning

2016-10-21T15:42:07+00:00

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 Signed-off-by: Bruce Ashfield

protobuf: Fix QA error for GNU_HASH

2016-10-21T15:42:07+00:00

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 Signed-off-by: Bruce Ashfield

go-cross: Fix failure if building go-cross first

2016-10-19T16:37:52+00:00

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 Signed-off-by: Bruce Ashfield

go-native: Add work around for binutils >= 2.27

2016-10-19T16:37:52+00:00

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 Signed-off-by: Bruce Ashfield

go-cross: Fix host contamination for x86_64 host to x86_64 target

2016-10-12T23:10:34+00:00

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 Signed-off-by: Bruce Ashfield

Revert "go-cross: Fix host contamination for x86_64 host to x86_64 target"

2016-09-24T02:02:19+00:00

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 target

2016-09-22T14:03:23+00:00

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 Signed-off-by: Bruce Ashfield

protobuf-c: uprev to 1.2.1 from 0.15

2016-09-12T14:03:04+00:00

Signed-off-by: Jianchuan Wang Signed-off-by: Bruce Ashfield