Update python3-docker-pycreds from 0.2.1 to 0.3.0.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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>
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>
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>
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>
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>
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>
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>
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>
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>
The openstack layer requires a version of six >= 1.9.0
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The go-cross-1.3 package depends on the libgcc to be installed for the
cross compiler else you will receive an error if this package builds
first like:
runtime/cgo
/opt/tmp/sysroots/x86_64-linux/usr/bin/arm-wrs-linux-gnueabi/../../libexec/arm-wrs-linux-gnueabi/gcc/arm-wrs-linux-gnueabi/4.9.1/ld: cannot find crtbeginS.o: No such file or directory
collect2: error: ld returned 1 exit status
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Since we need go 1.3 to co-exist with later versions (ie 1.4),
package go-cross_1.3 as go-cross-1.3_1.3.
go 1.3 will be installed to a different path than go-cross, this requires
go packages needing go 1.3 to set its PATH to:
export PATH=${STAGING_BINDIR_NATIVE}/${HOST_SYS}/go-1.3:$PATH
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: set alignment for the .rel.plt section on 32-bit architectures
This patch is cherry picked from golang's upstream, and this patch will
fix the package of etcd's following build error:
ERROR: debugedit failed with exit code 256 (cmd was 'bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit' -b 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi' -d '/usr/src/debug' -i -l 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/debugsources.list' 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/package/usr/bin/etcd'):
bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: elf_update: invalid section alignment
ERROR: Function failed: split_and_strip_files
ERROR: Logfile of failure stored in: bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/temp/do_package/log.do_package.109414
ERROR: Task 12 (layers/meta-overc/meta-pod/recipes-connectivity/etcd/etcd_git.bb, do_package) failed with exit code '1'
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: fix the building failed for quark bsp
Quark used i586 architecture, and golang dealt intel 32bit
architecture as 386, so export GOARCH = "386" when the TARGET_ARCH
is i586 to support quark bsp.
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: fix the bug of cross building error
When a package's recipe inherit "cross" bbclass, its CC and CXX are defined
as the host native gcc and g++ instead of the host cross toolchain, fot this
case, CC_FOR_TARGET and CXX_FOR_TARGET should be defined the same with CC and
CXX, instead they are should be define as host cross toolchain's CC and CXX,
otherwise, it will build failed for target arm architecture as below:
| # Building packages and commands for linux/arm.
| + CC='gcc '
| + bitbake_build/tmp/work/x86_64-wrs-linux-gnueabi/go-cross/1.4-r0/go/pkg/tool/linux_amd64/go_bootstrap install -ccflags '' -gcflags '' -ldflags '' -v std
| runtime
| errors
| sync/atomic
| unicode
| unicode/utf8
| math
| sort
| encoding
| unicode/utf16
| container/list
| crypto/subtle
| runtime/cgo
| container/ring
| image/color
| runtime/race
| # runtime/cgo
| gcc: error: unrecognized command line option '-marm'
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The current version of docker (1.6.2) requires go 1.3
See go 1.4 sqlite issue:
https://github.com/docker/docker/issues/9649
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Using a wildcard will simplify things when using meta-virtualization
against different yocto or oe branches and prevent having to make
future updates to keep in step with package uprevs.
The changes found within these bbappend tend to be generic and
non-version specific, thus safe for 'porting' via wildcard.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
From b101a0c7ce6ef1eb41bef786831e58fa4d1b069f Mon Sep 17 00:00:00 2001
From: Amy Fong <amy.fong@windriver.com>
Date: Mon, 27 Jul 2015 14:10:20 -0400
Subject: [PATCH] golang: use oe-meta-go
Update meta-virtualization to use go package from oe-meta-go.
The package golang-cross is go-cross in the oe-meta-go.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
golang doesn't work with ccache. In the current state, a lot of parsing
happens where it'll grab the first string in CC or LD and uses that for
its builds. When ccache is enabled, it results in trying to do builds
with just ccache.
The brokeness is seen when building with apps that uses cgo, like docker.
To enable ccache to work, some string comparisons and changes to parsing
had to be made.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
On glibc 2.20+, the _BSD_SOURCE and _SVID_SOURCE feature test macros are
deprecated as of glibc 2.19.90 (2.20 devel), we define _DEFAULT_SOURCE
instead.
(fixed upstream)
https://groups.google.com/forum/#!topic/golang-codereviews/S4TARFCxu2k
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The lack of a proper ability to regenerate configure causes the cross
compile detect logic to fail (shown below). It is easiest to just
force the cross compile option at configure time.
| configure: error: in `/opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/build/temp.linux-x86_64-2.7/libev':
| configure: error: cannot run C compiled programs.
| If you meant to cross compile, use `--host'.
| See `config.log' for more details
| Running '/bin/sh /opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/libev/configure > configure-output.txt' in /opt/buildtmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/python-gevent/1.0.1-r0/gevent-1.0.1/build/temp.linux-x86_64-2.7/libev
| building 'gevent.core' extension
| creating build/temp.linux-x86_64-2.7/gevent
| ccache arm-wrs-linux-gnueabi-gcc -march=armv7-a -mfloat-abi=hard -mfpu=neon -marm -mthumb-interwork -mtune=cortex-a7 --sysroot=/opt/buildtmp/sysroots/fsl-ls10xx -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -O2 -pipe -g -fPIC -DLIBEV_EMBED=1 -DEV_COMMON= -DEV_CLEANUP_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_PERIODIC_ENABLE=0 -Ibuild/temp.linux-x86_64-2.7/libev -Ilibev -I/opt/buildtmp/sysroots/fsl-ls10xx/usr/include/python2.7 -c gevent/gevent.core.c -o build/temp.linux-x86_64-2.7/gevent/gevent.core.o
| In file included from gevent/libev.h:2:0,
| from gevent/gevent.core.c:313:
| libev/ev.c:45:22: fatal error: config.h: No such file or directory
| # include "config.h"
| ^
| compilation terminated.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Uprev docker to 1.6.2
go-capability is upreved to a later git commit
go-dbus is upreved to version 2
go-distribution-digest is added as a new dependency. Only the
digest part of go-distribution is needed/kept here,
hence go-distribution-digest
go-logrus is upreved to 0.7.1
Remove PR since it's no longer used
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The ccache on some hosts will cause the golang-cross package to fail
with the error:
| cmd/fix
| cmd/yacc
| runtime/cgo
| go build runtime/cgo: no buildable Go source files in /proj/bitbake_build/tmp/work/x86_64-wrs-linux/golang-cross/1.3-r0/go/src/pkg/runtime/cgo
| WARNING: /proj/bitbake_build/tmp/work/x86_64-wrs-linux/golang-cross/1.3-r0/temp/do_compile/run.do_compile.14152:1 exit 1 from
| sh -x ./make.bash
| ERROR: Function failed: do_compile
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Work around an issue with python 2.7 not always having SSLv3 available
by allowing v2 or v3 certificates.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Docker's build process will clone missing dependencies which
circumvents the bitbake fetcher. This is a bad thing in many ways, for
example this will not respect BB_NO_NETWORK and DL_DIR settings. To
work around this we are able to provide recipes for each of the
missing dependencies.
The dependencies are all in GO and are required to be added to the
sysroot such that the docker build can find them via GOPATH at build
time. The docker recipe was updated to add these new packages as
dependencies and the explicit clone of go-cli was removed.
After these change we are able to complete the build with networking
disabled after completing a fetchall. Docker functionality was tested
on an image built with these changes and it functions as it did
before.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
These are a set of dependencies required to build and run docker and
docker-registry which had previously existed in
meta-cloud-services. By moving these from meta-cloud-services to
meta-virtualization we can build and use docker without needing to
include meta-cloud-services. Since meta-cloud-services depends on
meta-virtualization these recipes will still be available for use with
packages/images in meta-cloud-services.
There is a concern that meta-cloud-services contains many python
packages as there exists tight dependency for specific package
versions, this move does not prevent this tight binding from
continuing using various mechanisms made available to layers.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
This package is derived from meta-golang:
https://github.com/digitallumens/meta-golang.git
commit 3fa6c8af6b4762de2f4e6740e327a5a71c29e6e1
In the meta-golang version, golang depends on a gcc-cross that causes
conflicts with our toolchain. So the golang-cross recipe was extracted
and then the following changes were made to work in wrlinux:
- our TARGET_ARCH is x86-64, golang-cross wants amd64
- in the former recipe, compile fails because it can't find header files
and libraries because --sysroot is dropped. So I redefined the target
cc and target cxx as cc and cxx at the start of the compile rule since
cc gets redefined in there somewhere.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
This is the old 2.7.2 version and it will be found when the
2.7.9 version goes looking for the patch of the same name,
causing do_patch() to fail.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
It is questionable if we need this at all anymore (we probably don't),
but for now, there's no reason to not match the versions.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
redefining THISDIR and using FILESPATH is no longer required in a
"modern" bbappend, and in fact breaks other layers that also patch
python.
Removing THISDIR and using FILESEXTRAPATHS_prepend fixes both issues.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
