| Age | Commit message (Collapse) | Author |
|---|
|
Only include our versions of recipes if virtualiztions is in
DISTRO_FEATURE
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
fsnotify is changed to new repository on gihub, so adapt this chanage
accordingly to avoid fetch failure.
Signed-off-by: Yunguo Wei <yunguo.wei@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
multilib
The multilib gunicorn (for example lib32-gunicorn) fetch fails with
below error:
-- snip --
--2018-03-07 16:52:09-- https://pypi.python.org/packages/source/g/gunicorn/lib32-gunicorn-19.1.1.tar.gz
Resolving pypi.python.org... 151.101.0.223, 151.101.64.223, 151.101.128.223, ...
Connecting to pypi.python.org|151.101.0.223|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-03-07 16:52:09 ERROR 404: Not Found.
-- snip --
Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Per the original commit this was only included as a temporary measure
until the recipe was available in meta-openembedded. At this point the
meta-openembedded recipe is not only available but has been uprev'd
several times making it more suitable than the recipe we are now
deleting here.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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-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>
|
|
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 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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
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>
|
|
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>
|
|
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.
|
|
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>
|
|
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
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>
|
|
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 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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
Armin Kuster
Yunguo Wei
Jagadeesh Krishnanjanappa
Mark Asselstine
Abdur Rehman
Ricardo Salveti
Pascal Bach
Jason Wessel
Adrian Dudau
Bruce Ashfield
Khem Raj
Huang Qiyu
Paul Barker
Wenzong Fan
He Zhe
Jianchuan Wang
Venkateswara Rao Mandela
Zumeng Chen