gnutls doesn't depend on libgcrypt anymore but
wpa-supplicant does. So add it as a dependencie.
(From OE-Core rev: b5e0e0589dba0e3eb6fa070594c904fec6e6c3a8)
Signed-off-by: Valentin Popa <valentin.popa@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removes not needed or already merged patches.
Removes unused configure flags.
Tells gnutls to use the included libopts.
Removes libextra (not needed since 3.0.5).
(From OE-Core rev: 4e360033579b9501449798b2d118f786816a557f)
Signed-off-by: Valentin Popa <valentin.popa@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the move from meta-oe to OE-core XDG based launched was dropped
without noting it in the commit message, so fix that regression.
Gnome-session will now launch the calibrator again.
(From OE-Core rev: 64e0c8a7585a36964988f2f00ac89eda514d5f7b)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It's being used by e.g. gnome-session when Terminal=true is set in
.desktop files, like xinput-calibrator does.
(From OE-Core rev: 9a821d80b732a52574ac5c20b323966811828852)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It gets its wrong in detecting 64bit options
and OE we already pass the right options as compiler
defaults
(From OE-Core rev: ec3add1752a410fada04b4788c142b91ef63ffa3)
(From OE-Core rev: 32b826720626ec2d426ff7dbfe5607bc0dbd8082)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the structure to work with immutable bio_vecs
(From OE-Core rev: 09d3d8f97d6c60707b8dfb3fa5b04fa2efe6f6f6)
(From OE-Core rev: b32d57e5a807a634c411628af1688aec960ac6e7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need to use gcc-nm and gcc-ar to deal with slim objects
which are generated when using -flto
(From OE-Core rev: e6d84c9f4fef201217ada60711ecfb94bc5dc2e0)
(From OE-Core rev: 56dc32f128b3029c38381c7cc81f244fbd77416e)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patches explain the issue in detail but this is exposed
with gcc 4.9 in binutils 2.24
(From OE-Core rev: fc5c467b680fc5aef4b0f689e6988e17a9322ae0)
(From OE-Core rev: 4dfb8847ebf8aab90ad8888933468e2899c96998)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix upstream bug
https://bugs.freedesktop.org/show_bug.cgi?id=77060
gcc 4.9 now generates slim objects when LTO is used
These slim objects only contain intermediate language
representation for LTO. Use -ffat-lto-objects to create files which
contain additionally the object code. When linking some .so file, the option
'-flto' is missed, so the error happens.
We add '-ffat-lto-objects' flag to make gcc 4.9 behaves the same as gcc 4.8.
(From OE-Core rev: c4e65e14fbdf957aa34e074337c5649a0b0888b7)
(From OE-Core rev: 858f01ab9613c2b122718c350da763f8fe981d9f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The scripts extact variable values from bitbake -e. Unfortunately
TARGET_ARCH is unset from that environment so we use TUNE_ARCH instead
which will have the value we need.
(From OE-Core rev: b77494025b3d47fd5130ae6c445ac84cabb1f91e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
mkhelp: generate code for --disable-manual as well
This allows configure --disable-manual to run and build without having
to regenerate the src/tool_hugehelp.c file which otherwise is necessary
since we ship tarballs with that file present.
(From OE-Core rev: 544a96255203a6779d1f0022d003c6680f330511)
Signed-off-by: Tudor Florea <tudor.florea@enea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the power were to fail, it doesn't matter to us much if the data
makes it to disk or not, we'd have other problems. However an fsync()
call on a multi build autobuilder is painful so lets avoid them.
(Bitbake rev: 4eb2dc8048e2722d64d589f453df1ce6262c71b8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the power were to fail, it doesn't matter to us much if the data
makes it to disk or not, we'd have other problems. However an fsync()
call on a multi build autobuilder is painful so lets avoid them.
This is particularly true in this case if a timeout causes a reconnect
during a build.
(Bitbake rev: ec28256ac2a30f047585e8f61200d764bc295ded)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently if you do localdata.getVar, the code parser simply ignores
the references. Change the code to use endswith() to catch more of the
references. These names are probably unique enough to get away with this.
Bump the cache version to ensure things get updated.
(Bitbake rev: cf763cddc3faa2361b4c4dbd08419e4ebabf208f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a fix about to go into bitbake to ensure that datastores
being accessed with a name other than "d" are correctly reflected
in checksums. This will cause this function to add in a number of
dependencies we don't want.
These do need to be properly unravelled in due course but would
only really affect multilib builds. For now therefore just exclude
the variables as per the old behaviour.
(From OE-Core rev: cbc41a573dd3a073e7b862ca9d763ce815e8f927)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows us to remove the following uses of PRINC in meta-raspberrypi:
recipes-bsp/formfactor/formfactor_0.0.bbappend:
PRINC = "1"
recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend:
PRINC := "${@int(PRINC) + 5}"
(From OE-Core rev: cffbd11d915fe8a1399f23c97c4e2ecbdae4d00a)
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The class itself currently does nothing. The idea is to mark all recipes that
make use of the texinfo utilities. In the future, this class could be used to
suppress the generation/formatting of documentation for performance,
explicitly track dependencies on these utilities, and eliminate Yocto's
current dependency on the host system's texinfo utilities.
(From OE-Core rev: e6fb2f9afe2ba6b676c46d1eb297ca9cc532d405)
Signed-off-by: Max Eliaser <max.eliaser@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Within the OE build environment, we supply the correct fpu settings. These
only need to be spelt out for the on-target gcc.
Doing this means the checksums for the core compiler don't depend on the fpu
settings. We exclude the compiler tunes for similar reasons, it doesn't need
to influence the compiler build.
(From OE-Core rev: ce1f3fd20d81545d6d5dfc68f86f9fddf8ac9bbf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we no longer build target libs within gcc-cross, we can drop the
TARGET_CC_ARCH flags and hence make it independent of tune.
(From OE-Core rev: 74d8866814aec520822518cc4cb8a942f7069bf7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The PKG_CONFIG definitions should now more closely match those from native.bbclass.
We can't use ${libdir} here since it contains the target arch prefix.
(From OE-Core rev: aebb71afe54b266de39ec7e1caf84e6426aaafba)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gcc-cross technically depends on the C library however we can use
one toolchain for multiple different tunes within a given architecture.
Manually remove these dependencies so that gcc-cross isn't rebuild with
every tune change.
(From OE-Core rev: 97df4e8e61a7693d548c3145e36f1d5503e91d03)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Unfortunately expandKeys() notices overlap between the SDK and TARGET
PREFERRED_PROVIDERS entries when we set things up for the SDK recipes.
To avoid this, delete one of the sets of keys to avoid supurious warnings.
(From OE-Core rev: 9068a65baf4a28d04efad9297b16a2883ac42689)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We should be explicit about the providers for the SDK toolchain so
add entries to do this.
(From OE-Core rev: fba380a2a37f04de04c0626c0a09cfe757c24341)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The metadata started using the bb.utils.contains_any which has been
add in the BitBake 1.23.0 release, set this as the minimal version to
ensure parsing compatibility.
(From OE-Core rev: dea40c2850a32b5b67e90336f9565889f92dabe8)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update PREFERRED_PROVIDERS after cross tooling name change to include PN.
Also drop the now obsolete gcc-intermediate which no longer exists.
(From OE-Core rev: 5cbb5c12a5656915c3c9752187b54ef095d42828)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Based on BeagleBoneTarget, this provides support for deploying images
and running tests on an EdgeRouter Lite (edgerouter). The device must
be set up to boot into the master image already - see the instructions
in the file.
Implements [YOCTO #6253].
(From meta-yocto rev: 6e28284f0dacb40f7533161bfaeb637723297947)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With a serial connection and beaglebone setup correctly as per
README.hardware (nand erased, default uboot config assumed, etc) and a
correctly deployed core-image-testmaster, we could actually deploy and
test AB built images.
In the default configuration u-boot will do the right thing and will
always boot into the master image (rootfs on second fs on the card,
kernel in /boot on the same partition). We just need to tell it for the
test image to use the third partition and update the kernel cmdline.
Pexpect is used to interact with whatever serial connection we have
(which for this target is mandatory).
There is some handling for images that don't contain the kernel and
dtb files as needed (such as core-image-minimal).
Implements [YOCTO #6252].
(From meta-yocto rev: 8235464faf480811b17b062cb9aad8ebf1cd2a67)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For use outside of tests themselves, we want a better error than
AssertionError, so create one and allow us to request it when calling
runCmd(). This enables us to avoid tracebacks during master image
operations if the power control command fails.
(From OE-Core rev: 89868383685091b0d3723fb8f29590f3f6610078)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you want to do automated hardware testing but don't have a
controllable power strip this script can be useful so that you know when
you need to cycle the power.
(From OE-Core rev: f71e9fe7c31fa44f5185d9ab64813ba2af57ca2a)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When running automated tests (or just generally interacting with)
boards whose serial console devices are on the board itself and thus
disappear when powered down or practically disconnected, such as the
BeagleBone white, some terminal programs (e.g. picocom) will exit when
the device disappears and need to be restarted after the serial device
returns. This script handles this automatically for such terminal
programs.
(From OE-Core rev: 0537269df779532245eb2954e04fc26b3edfed85)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we couldn't start the target, it doesn't make sense to try and stop
it here since logically it shouldn't now be in any kind of "started"
state. (It's the start function's job to clean up after itself if it
fails - to that end, fix up the QemuTarget class so that it does.)
(From OE-Core rev: 819ebddae6b78120e5e082423793ff988419b5c4)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of powering up the target when the object is constructed, wait
until deploy is called. Then there are basically two different
scenarios:
a) The device is booted into the master image already, in which case
we can just use it
b) The device is booted into another image or can't be contacted, in
which case we need to power cycle it. Here we also now wait until it
has booted up instead of trying to contact it immediately.
(From OE-Core rev: c2257fa50071e4704a8152b5f1d16f899b4bed98)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Similar to power control command, this depends on a user's setup to get to
the serial port of a board. For a local connected board this could just be:
TEST_SERIALCONTROL_CMD = "picocom /dev/ttyUSB0 -b 115200"
and for a serial console server: "telnet 10.11.12.13 7003" or some conmux
command.
(From OE-Core rev: 5131094ad8f53b2052a97efd505e7a170d0c915d)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
And drop the un-needed and un-used restart methods.
Only qemu ever used this and actually does it safely.
(From OE-Core rev: 1dd1edb5ea551c8a01538b130aa4d0c361eae14d)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Right now GummibootTarget is the only hardware TEST_TARGET with deployment,
but we will add more, so let's make an abstract base class, that will
do the common thing for all the hw targets.
(From OE-Core rev: 1d70b1908e1dc5d612b0627022659639e3f384e5)
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Regardless of the numbering used in source archive filenames, the
upstream version number is in dotted form in documentation, release
notes and the website, so we need to be using that here since that is
what people will expect to see.
(From OE-Core rev: b8f82a8808b0d217815b30ed06efc8a0be4494a5)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
