mirrors.bbclass already adds downloads.yoctoproject.org/mirror/sources for FTP
and HTTP to ${MIRRORS} so there's no need to do it again.
(From meta-yocto rev: 67b79df4fbffcf677f8d127c00672f0d7c6c434b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This overrides the default assignment in qemu.inc and in doing so removes
RISC-V.
(From meta-yocto rev: 8cc9423649b2702c0ded721244a017b371b3a244)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If DISTRO_VERSION is defined using an override, e.g., by defining it
in auto.conf as DISTRO_VERSION_forcevariable, then the unoverridden
value was still used in SDK_VERSION since it was defined using the :=
operator. However, there should be no reason to define SDK_VERSION
this way.
Also use getVar to access the variable to ensure tracebacks from problems
are less confusing.
[RP: Tweaked commit message]
(From meta-yocto rev: 74f43fb82a93eecfe7519a87fdf1cb0152d56b48)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replace SDK_ARCH with SDKMACHINE so that SDK targeting different
development machines but having the same architecture don't cause
similar errors as found in '3614dd4aee9 ("poky.conf: Add MACHINE to
SDK_NAME")'
This doesn't have any effect on the SDK machines provided in oe-core,
since SDK_ARCH is the same as SDKMACHINE for all of them.
(From meta-yocto rev: 951184fd62b3ab14266f300defd47d3c5c09ad9b)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Avoid errors from:
MACHINE=qemux86-64 bitbake core-image-sato:do_populate_sdk
then:
MACHINE=genericx86-64 bitbake core-image-sato:do_populate_sdk
which gives:
ERROR: core-image-sato-1.0-r0 do_populate_sdk: The recipe core-image-sato is trying
to install files into a shared area when those files already exist. Those files and
their manifest location are:
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.host.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.testdata.json
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.target.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.sh
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
Please verify which recipe should provide the above files.
Adding MACHINE to the artefact name will avoid this. The issue was highlighted by
changes to the autobuilder configuration.
(From meta-yocto rev: 3614dd4aee9d19f1024edb6a36b2862c2d726c04)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, this is a QA warning by default, howver its a useful
check to catch configuration errors, where we might have forgotten
to update or adapt configure options on updates/upgrades to a package
(From meta-yocto rev: a75ad2e4227f715146fc1e07f9abef4e80c1aa12)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4.18 will be the newest kernel in the upcoming release, so we bump
our default to it in preparation of 4.15 being dropped.
(From meta-yocto rev: 698c1edd9a258a891b7f1373c3468218e6440856)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This has been an opt-in for so long, some distributions e.g.
poky-lsb uses it by default however, since most of linux
distros have started to default to these settings for security
enhancements, time has come for OE to make it default too
(From meta-yocto rev: 81bf1019c8601da952242fbcc827e0bef1ff25d7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the default kernel for qemu* to be v4.15. This allows easy
integration of the latest fixes/features for new BSPs. 4.14 is also
available as a LTS kernel option.
(From meta-yocto rev: cdd79c0f879e5e4c480773c4507f921533e17914)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fedora 24 reached end-of-life on 2017-08-08 and hasn't been tested in
some time.
* Fedora 25 reaches end-of-life in Q4 2017 and is exhibiting a bug which
makes it an extremely unreliable host OS for workers on the Yocto
Autobuilder. For that reason we'll no longer be using this distro on the
Yocto Autobuilder and thus cannot claim the distro is sanity tested.
(From meta-yocto rev: 976ee9a60ab786ae07057577975e3b91e388cd47)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have been working with OE on debian-9 for several months now without
issue. In addition, I tested a build + runqemu for core-image-sato
following the quickstart guide and had no issues.
(From meta-yocto rev: 2d8a572df7498ce8eb3a78f05384f0f7dd5ecb91)
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This should have been done after Pyro was released, but it apparently
slipped though the cracks.
(From meta-yocto rev: 4e6dc6596fd60c35e14ad95899ebd66d16375d77)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Things to note:
* This ends up enabling dri3 in mesa
* It does not completely enable dri3 in xorg with xf86-video-intel
because that requires a run time configuration (xorg.conf)
So vulkan in poky with xf86-video-intel still requires a xorg.conf
snippet to enable dri3. Otherwise (weston or X with other drivers)
it just works.
(From meta-yocto rev: f55e894b7fb9fa6974e8048032a8373073738f9e)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
tested the quickstart guide on Fedora 26 and confirmed that it
can build a core-image-sato and run the image via runqemu.
(From meta-yocto rev: 4e719fb77d035123d0e2ff84d10cb68c7cc8eccd)
Signed-off-by: Benjamin Esquivel <code@esquibits.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch removes the machine specific overrides in poky.conf for all
the qemu machines. With this patch, if you set
PREFERRED_VERSION_linux-yocto="X%" then all the qemu machines as well as
the sample hardware boards will use that version. Without this patch,
the hardware boards would have used version X but the qemu machines
would have needed to have a PREFERRED_VERSION_linux-yocto_qemuarm="X%"
for qemuarm to use that version, for example. If we need to force a
specific machine (hardware or qemu) to a particular default version we
should add it to the machine conf files for that machine, not in the
distro conf.
(From meta-yocto rev: 6b194a137dcedcae7e4b03f9ebed822d44f53fe2)
Signed-off-by: brian avery <brian.avery@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new Ubuntu releases on 2017-04-13, after cutoff for Yocto Project 2.3.
I've been running builds of some images and a world build in a container
over the past couple of days without issue. I've also run a complete
oe-selftest run (with SANITY_TESTED_DISTROS = "") and did not observe any
errors.
(From meta-yocto rev: ecdaf38e0b6beaeaf8ea7f804ca73a18f0dbe371)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove several old/untested distros from the list:
* poky-1.8 and poky-2.0 are no longer supported releases
* ubuntu-14.04 is an LTS but we plan to remove it from the
project's autobuilder cluster as the kernel is old and
it doesn't use systemd -- therefore this will no longer
be tested.
* ubuntu-14.10 and ubuntu-15.10 are no longer supported
* fedora-22 and fedora-23 are EOL
* opensuse-13.2 is discontinued
Add opensuse-42.2, it's the openSUSE version we run on the Yocto
Project autobuilder cluster.
The distro support plan is documented on the Yocto Project wiki:
https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan
they are easily summarised as:
- Fedora: most recent 2 releases
- Ubuntu: most recent LTS and latest release, unless they are the same
in which case the most recent 2 releases
- CentOS: latest release
- openSUSE: latest release
(From meta-yocto rev: ba5ad19cbe9066823fe3a3b432a893f4cf67be47)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have tested Fedora 25 enough times to add it to the tested distros
list. Additionally, in Guadalajara's staging autobuilder has been
tested for some time now so it is safe to put it in.
(From meta-yocto rev: c6ac52f061207e8fcedebda0ca4279fa5b07b9a6)
Signed-off-by: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I'm this locally on my build machine so its likely to work.
(From meta-yocto rev: df2bdba3b96ae0957fee5065befa569fc940b5e3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The distribution identifier determined by oe.lsb.distro_identifier()
is now returned as a lowercase string. Update the values for tested
distros to match.
(From meta-yocto rev: cb171bdc9b8dc485b25b9176949427f6d755aeec)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemu-system-mips64el is unavailable which causes problems for runqemu
Add mips64el to QEMU_TARGETS to build it.
(From meta-yocto rev: 98063183ecbe18750ee7036e71bbbbb3044a13ac)
Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The autobuilder can't cope with this version format, work around
the issue for now.
(From meta-yocto rev: ea1a72ed3ae0ad072d6583920bf8a94448c97f9e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We've had a builder in the Yocto Project Autobuilder cluster
using Fedora 24 for some time now, I think it's safe to say it's
tested.
(From meta-yocto rev: 8774ecd08f36858db3f047b41d91113ed20aa6be)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This enables the 4.8 kernel nby default for the qemu machines.
(From meta-yocto rev: 2dd82f25a365070b79f0f2d6b4eb2c6e793c74f9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We're no longer building CentOS 6, Debian 7 or Fedora 21 on the
Autobuilder cluster.
(From meta-yocto rev: e4d81d1bcd8aa3ecdd247b8c05a015a87f10cb5e)
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
DATE is in HASHCONFIG_WHITELIST which means the server does not reparse when
DATE changes. If DISTRO_VERSION was used somewhere and contained DATE, the
value *would* change however, meaning the server and worker checksums
could end up differing.
We therefore exclude DATE from the checksums, making everything consistent.
(From meta-yocto rev: b5d6379ab9484acd3ea22fa9faeeaf0a1e2c2550)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use uninative by default, not least to benefit from sstate cache reuse on
the autobuilders.
(From meta-yocto rev: 22e788f73528103b9927e7ffc75e509e51c2ffa9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
"poky" is the reference distribution for the Yocto Project. This renames
the layer within the meta-yocto repository to meta-poky, better matching
what that layer contains.
A layer.conf file is left behind as this is the only way which allows
existing builds to migrate safely to the new name. It will be removed
at some future point.
This change requires the corresponding OE-Core change to handle the
migration and the changes to the infrastructure to support this.
(From meta-yocto rev: d0c88df2e14672fca4ebbde93c5efbcd0e4fa9b6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
