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>
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>
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>
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>
We need to ensure we are using the target toolchain and sysroot to
avoid possible host contamination, and in the case of non x86-64
target builds, allow the build to complete successfully.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
getent is needed by lxc-net of lxc, but current system misses it,
so add glibc-utils to lxc's rdepend, fix this issue.
Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When do split_and_strip_files, it may calls debugedit to deal elf files.
For ptest sub-package, it fails to run debugedit with .o files. So remove
the .o files which are redundant to run ptest cases.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
A newer version of the recipe is maintained in meta-openembedded/meta-oe.
No reason to keep an older version here.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Add Native Linux KVM tool, a lightweight tool for hosting KVM guests
maintained by the Linux kernel community.
Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
Add missing test helpers
We don't support windows encoding so remove that case
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
The python-newrelic package is licensed under several licenses,
including the customer NewRelic license. This has been properly
captured in the LICENSE string in the recipe but since there is no
copy of the license it isn't copied into the package's build
license-destdir which results in the following warning:
WARNING: core-image-minimal-1.0-r0 do_rootfs: The license listed
NewRelic was not in the licenses collected for recipe python-newrelic
Add a copy of the license to the layer's custom-licenses folder to
resolve this warning. The license text comes verbatim from the
upstream LICENSE file.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This is a small package so despite the large version jump the changes
are minor, mostly bug fixes and some work around systemd.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Seems upstream adjusted their LICENSE file. The license is still
Apache version 2 so no worries about having to update the LICENSE
string for the recipe.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Systemd takes care of setting up the various cgroup mounts at boot,
and likewise the tearing down of these at shutdown. It is therefor a
useless dependency when we are using systemd.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Apparently if a license is listed for a package it must be included in
the overall LICENSE variable otherwise you will get WARNINGS such as:
WARNING: LICENSE_libvirt-ptest includes licenses (LGPLv2.1 GPLv2+)
that are not listed in LICENSE
We ensure that the license string is consistent between the LICENSE
variable and the subpackage license string to remove this
warning. Since '2+' is a superset of '2', ie. "version 2 or later",
and actually is more reflective of the text found on the file headers
and such we use GPLv2+ and LGPLv2.1+.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When build for architecture that don't use gcc atomic ops but pthread,
it fails to build for arm:
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In function `virClassNew':
| /buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:153: undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In function `virObjectNew':
| /buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:205: undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In function `virObjectUnref':
| /buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:277: undefined reference to `virAtomicLock'
| ../tools/nss/.libs/libnss_libvirt_impl.a(libvirt_nss_la-virobject.o): In function `virObjectRef':
| /buildarea2/kkang/builds/qemuarm-Aug03/bitbake_build/tmp/work/armv5e-wrs-linux-gnueabi/libvirt/1.3.5-r0/build/src/../../libvirt-1.3.5/src/util/virobject.c:298: undefined reference to `virAtomicLock'
| collect2: error: ld returned 1 exit status
It is similar with:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=12dc729
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upgrade libvirt from 1.3.2 to 1.3.5.
* update checksums and remove PR
* remove trailing whitespace
* remove backport patch 0001-fix-crash-in-getAllDomainStats.patch
* update context of patches
* remove libvirtd.socket from SYSTEMD_SERVICE which doesn't exist anymore
* install test data which ptest requires
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce@zedd.org>
Currently libvirt python builds in the multilib case, but fails to
install. Switch from PN to BPN, and fix compile to be consistent.
Signed-off-by: Bruce Ashfield <bruce@zedd.org>
- update packages and add additional ones for new binaries
(cpuid and livepatch)
- update xen_git to point to 4.7, make branch= fully variable,
and remove assumed .0 from release version
- add patch to fix compilation of xen with gcc 6 on arm/aarch64
Build tested x86_64 and aarch64 targets.
Signed-off-by: Chris Patterson <pattersonc@ainfosec.com>
Signed-off-by: Bruce Ashfield <bruce@zedd.org>
openvzutilstest.conf file is needed by openvzutilstest test
Signed-off-by: Catalin Enache <catalin.enache@windriver.com>
Signed-off-by: Bruce Ashfield <bruce@zedd.org>
Bumping the version of docker and dependencies. This gets us closer to
runc 1.0, which is the foundation for future OCI efforts.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The docker build isn't properly using CFLAGS/LDFLAGS, which triggers the following
QA error:
ERROR: docker-1.11.1+git5604cbed50d51c4039b1abcb1cf87c4e01bce924-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary: 'docker/1.11.1+git5604cbed50d51c4039b1abcb1cf87c4e01bce924-r0/packages-split/docker/usr/bin/docker' [ldflags]
ERROR: docker-1.11.1+git5604cbed50d51c4039b1abcb1cf87c4e01bce924-r0 do_package_qa: QA run found fatal errors. Please consider fixing them
ERROR: docker-1.11.1+git5604cbed50d51c4039b1abcb1cf87c4e01bce924-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: tmp/work/core2-64-overc-linux/docker/1.11.1+git5604cbed50d51c4039b1abcb1cf87c4e01bce924-r0/temp/log.do_package_qa.63906
ERROR: Task meta-virtualization/recipes-containers/docker/docker_git.bb:do_package_qa (meta-virtualization/recipes-containers/docker/docker_git.bb:do_package_qa) failed with exit code '1'
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Upgrade iasl from 20120215 to 20160527
* Fix the dependency as it actually depends on
bison-native and flex-native
* Remove hardcode PR to let PR server handle
the version
* Add (x86_64.*|i.86.*)-linux to COMPATIBLE_HOST
* Add patch Make-CC-definition-conditional.patch
to make CC definition conditional as it makes
the package unable to cross-compile when hardcode
CC's definition previously.
* Add iasl command manual file as iasl.1
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
If the lxc is compiled with gcc 5.2 -O2 optimization on arm,
lxc-console/lxc-stop command always produce segment fault.
The same issue also occurred on systemd: [YOCTO #8291]
For lxc, after several testing, it only needs to disable
schedule-insns2 to fix the segment fault issue.
Signed-off-by: fli <fupan.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This approach breaks images which have Xen in DISTRO_FEATURES,
but are not booting under Xen (and mounting /proc/xen fails).
xencommons, xendriverdomain, or proc-xen.mount should take care of
mounting /proc/xen.
Signed-off-by: Chris Patterson <pattersonc@ainfosec.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
netns is a runc hook for setting up simple bridge networking within containers.
See README.md (or https://github.com/jfrazelle/netns/blob/master/README.md) for
instructions on how to use netns.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When building for qemux86 the following error was encountered due to GOARCH
being set incorrectly:
compile: unknown architecture "i586"
This can be fixed by using the go-osarchmap class.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Some recipes in RDEPENDS are installing specific version of package, for
example:
gunicorn (= 19.1.1)
If usigin ipk for PACKAGE_CLASSES, opkg prints error:
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies
for docker:
* gunicorn (= 19.1.1) *
* opkg_install: Cannot install package docker.
This error is caused because opkg appends package revision to version.
In this case:
gunicorn_19.1.1-r0.1
If we use comparator >= this error doesn't appear.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
It shows warning when build crius if libselinux has been built already:
WARNING: QA Issue: criu rdepends on libselinux, but it isn't a build dependency? [build-deps]
Add a patch to disable selinux support when 'selinux' is not in PACKAGECONF.
And update indentation at same time.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Usually $GOROOT is set by go tool, but if sstate is specified, $GOROOT
is set to the path in the first project. If docker is built in the
another project(with same SSTATE_DIR) later, and the first project is removed,
the following error will be seen:
| go: cannot find GOROOT directory:
/path/to/previous/project/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/x86_64-wrs-linux/go
This commit is overriding $GOROOT stored in the go tool in sstate cache,
making sure it is set to the correct path in current project.
See more information here: https://golang.org/doc/install#install
Signed-off-by: Yunguo Wei <yunguo.wei@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
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>
Upstream libvirt Commits 1d39dbaf and 827ed9b4 broke the libvirt-python API
by removing virDomainRef() and virDomainFree(). virDomainStatsRecordListFree() will
free that domain pointer and later when virDomain (python object) call
its destructor and tries to free that same pointer again.
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
Since CRIU does not explicitly nominate the version of protobuf as 2.6.1, which
should not be included just here. And it seems protobuf-2.5.0 is doable or this
CRIU version based on a basic testing according to criu.org/Simple_loop as well,
so remove it from criu.
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
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>
