Surfaces on uclibc where libiconv is not coming from libc but from
separate package.
Change-Id: I8eef52a69d2b6830deff94531631ca098bce2a89
(From OE-Core rev: 2ffcba096125b904d83508368cec56b6224fc2e1)
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>
An agressive optimization in gcc5 meant that we get linking errors
with uclibc build, this patch fixes the issue by letting gcc know
that these funcitons are used.
Change-Id: I8ecf3999a0855b3bbf4bc2df576be5351f9be5b0
(From OE-Core rev: 458bfefecdd2b5e2efa743f29d3dc8b3471e6df1)
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>
The 0001-uclibc-nss.patch has been applied upstream
in a bit different way but solves the issue at hand
Change-Id: I7312d109d01c08338d4673383e2eaccee219b7bd
(From OE-Core rev: 8b84e778fb481075d245e1d5cc1b3b81024681d5)
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>
This patch fixes a small bug that prevents seting a git repo in exported SDK
layers dir. Before setting a git repo, that directory needs to be created.
[ YOCTO #6659 ]
(From OE-Core rev: 47860e483d7a9b4440d1ed9bd96d724370887f58)
Signed-off-by: Costin Constantin <costin.c.constantin@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since the log_check_regex can potentially be false positive it
makes sense to print the whole line where error is found.
This way user will be able to see the error and understand
if it's valid or not.
[YOCTO: #7789]
(From OE-Core rev: f9cf31525fc885e1a0f65bd55654631257f87078)
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Automatically export public key(s) of the signing key(s) from the gpg
keyring. Adds a new simple recipe that does the actual task of exporting
the keys. This patch makes the RPM_GPG_PUBKEY and PACKAGE_FEED_GPG
PUBKEY settings obsolete.
(From OE-Core rev: 23b30c34581948e1ea02c25cbf7b9194d7e49fb8)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed package feeds are not yet implemented for these package formats.
(From OE-Core rev: 49a5c8700deddac744ccfa033bebf7971f92e14b)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After this change signed package feeds should be enabled by adding
INERIT += "sign_package_feed"
instead of definining PACKAGE_FEED_SIGN="1".
(From OE-Core rev: 2ba901da9a07350cc8975fc951ef5054b32d421b)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Simplifies the configuration. Makes way for the removal of
RPM_GPG_PUBKEY setting and possible future implementation of a separate
signing server support. Also, moves the configuration sanity checking
into a separate function.
(From OE-Core rev: 6ea062dffce3df59cc4ba88edd181dc1dac759f9)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If defined, use GPG_PATH as the gpg home directory when signing package
feeds. This setting is only used by package_manager if package feed
singning has been enabled, i.e. PACKAGE_FEED_SIGN="1".
(From OE-Core rev: 2c94853e4c8e92ac5fe4af7b25e2ce8853a4025b)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This bitbake configuration variable can be used to define the gpg home
directory.
(From OE-Core rev: 7ea2f8aca832433f448a79d103c945a63ac6474b)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If ccache is enabled, compiling apr-utils fails with the following error
messages because libtool is confused by the "ccache gcc" appearing on
the command line. Disable ccache for apr, so that ccache don't get
enabled in all software using apr's rules.mk.
The error message from apr-utils-native:
(From OE-Core rev: 3533552050d0f91b669c6939755c5f6efefa9d58)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the META SRCREVs to make the nf_tables feature available.
(From OE-Core rev: 43ed2494ae4f89cab6e018f289bb048289d478f5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to apply the same fix as 3.14 and 4.1 already
have to fix qemuarm boots with gcc5.x
[YOCTO: #8415]
(From OE-Core rev: fa9852d5d7383e6d03c756b8ad615668857b0b86)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Before the fetcher validated the specified SRCREV was reachable on a
specified branch, linux-yocto style kernel's were comparing the value
of KBRANCH and branch on the SRC_URI and then allowing a SRC_URI
specified branch to override KBRANCH.
With the introduction of kernel meta data on the SRC_URI, this routine
is incorrectly picking up a kernel-cache repository and then attempting
to apply that branch information to the kernel repository.
The rationalization of the branch specification is largely no longer
required, and will may be removed in the future. But for now, to keep
changes minimal, we can simply not return branch information that comes
from kernel meta data by checking the 'type' parameter and skipping
if it is of type 'kmeta'.
(From OE-Core rev: 87363ec019e04b486dee5f07b7226465be7acd6c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the recent changes to improve patch processing times, the ability
to skip already applied patches is not active by default.
The automatic detection and resume was hiding issues with the include
files generated by scripts like yocto-bsp.
If a .scc file that contains a patch is included twice, the patch is
applied twice, and the second appliation fails for obvious reasons.
We can partially fix this by ensuring that already included
configuration fragments are not forced into the meta-series.
.scc files that are explicitly listed twice will continue to fail, and
recipes must be modified to avoid this.
[YOCTO: #8486]
(From OE-Core rev: ed2da98bf3ac798009f58a53b91285b4dac69d5a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 4.1 SRCREVs to integrate the following fix:
[
drm/i915: Fix the VBT child device parsing for BSW
Recent BSW VBT has a VBT child device size 37 bytes instead of the 33
bytes our code assumes. This means we fail to parse the VBT and thus
fail to detect eDP ports properly and just register them as DP ports
instead.
Fix it up by using the reported child device size from the VBT instead
of assuming it matches out struct defintions.
The latest spec I have shows that the child device size should be 36
bytes for rev >= 195, however on my BSW the size is actually 37 bytes.
And our current struct definition is 33 bytes.
Feels like the entire VBT parses would need to be rewritten to handle
changes in the layout better, but for now I've decided to do just the
bare minimum to get my eDP port back.
Cc: Vijay Purushothaman <vijay.a.purushothaman@linux.intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit 90e4f1592bb6e82f6690f0e05a8aadcf04d7bce7)
Signed-off-by: abdul arif abdul muttalib
<abdul.arif.b.abdul.muttalib@intel.com>
Signed-off-by: Tan Jui Nee <jui.nee.tan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
(From OE-Core rev: 1f575df04f003c1e1fe9413f95023c20a2f30e19)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the configuration fragments for the Intel Axxia on the 3.14
and 4.1 kernels.
(From OE-Core rev: a4964955257a1ab2586fd5efeedc2e32b725895d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS won't always grab your
out-of-tree module recipe since the kernel recipe's
PACKAGES_DYNAMIC variable provides kernel-module-*. This
patch documents that your out-of-tree module needs to explicitly
set its PACKAGES variable to avoid this behavior.
(From yocto-docs rev: 2c51eae23b634cdace5a119ee1a6c8e8ba76dc45)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed [YOCTO #8168]
I placed a couple notes in the "Configuration" and "Compilation"
sections within the "Writing a New Recipe" section. These notes
point out that the build system (as of release 1.7) now disables
several *-config scripts. The user should be using "pkg-config"
to ensure proper pathname construction and location of these
types of scripts.
(From yocto-docs rev: a46fd0f7b4d5da7bf3b218441ec5b9a6ef552266)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I was refering to the class as "pkg-config". This was incorrect.
I fixed it in the opening sentence to use "pkgconfig".
(From yocto-docs rev: c8400b362704093d4c2c891f521c11818eb506a8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In Section 5.5.3.2 bb.fetch.encodeurl: Use bb.fetch.encodeurl
changed to
bb.encodeurl: Use bb.fetch.encodeurl
Reported-by: Olivier Dugas <dugaso@sonatest.com>
(From yocto-docs rev: bec0f98f2383b231a1d453932a14b07038febd36)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8298]
Updated several classes with feedback from Jose Lamego of Intel.
The feedback fixed some class groupings so that previously isolated
classes could be bundled under common classes (e.g.
autotools*.bbclass).
I scrubbed the cross-references for cases where a particular
class became "undocumented." The cross-references now point to
the bundled class entry in the ref-manual.
(From yocto-docs rev: 07a533cb41ad26d202f4e303f2dbc7d7bf26e076)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCOT #8301]
Added descriptions for PACKAGE_FEED_ARCHS,
PACKAGE_FEED_BASE_PATHS, and PACKAGE_FEED_URIS variables.
The build system uses these three variables to construct a
set of final package feed URIs.
(From yocto-docs rev: 53447af460932caa5b2b7637894657eb9fd2e84d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8439]
The "image-swab" class depends on "strace" package being on
the build host. I added that fact to the note where we say
the class is not maintained.
(From yocto-docs rev: 503f4199b3c0bcfcd333dbab025b40f9508a6820)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new section in the interface use area that describes
how to build a version of a recipe that is not the default
version. Four new figures were added to support the
description.
(From yocto-docs rev: 232a875fb8fff97ce0578cf50b2a102bdaed1758)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note strongly suggesting that the user should set up
this virtual environment even though it is not required.
(From yocto-docs rev: 1e5f5c7e36eb8541d0d0e2c7e5d37d65c84946bf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8428]
The changes to the .json file are now shown in the documentation.
(From yocto-docs rev: 5636632f0a2f0d79d632c72037c4306cfad3ec75)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8412]
Forgot about CentOS. I have added that item in.
(From yocto-docs rev: f298ef74d7366ef01b9b1efcf5b0824a6e1aa742)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8419]
There was a typo in the section that indicated the file extensions
for various Package Management Systems. The one for RPM used a
file extension of ".rms". I fixed it to ".rpm".
(From yocto-docs rev: 7b303a789d4f11aed6ebc83d734a27442a531b52)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the SRC_URI variable description to cross-reference
the "Fetchers" section in the BitBake User Manual and added
some more Fetcher URL parameters specific to certain fetchers.
This was done to help clarify how to put fetched code into
specific directories.
Also updated the bin_packages.bbclass description to have a
better example. Used a git:// fetcher example and provided
some specific URL parameters.
(From yocto-docs rev: 7133b49092096c253ffce99f39d4fa6db7810061)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section for setting up a Python virtual environment has
gone from "optional" to "required". I re-worded the section
as such.
(From yocto-docs rev: 3a20244c8b0b594723c0b35c8808bb96a210d63a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8412]
Added another bullet item that lists the required packages per
distributions needed to enable the runtime QEMU tests.
(From yocto-docs rev: f7e42f9b069e0fd3b419b571554669a89bc843e6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The wrong command was in the help example in the note.
(From yocto-docs rev: a1ba70d1dcc680c2ddfb8fd5c544f57a29745cbc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These updates included editing the poky.ent file so that
DISTRO and related variables are now 2.0. Also updated all
the title pages to have the manual revision table correct.
Finally, used my email for the manuals.
(From yocto-docs rev: deae61bfbb528ea0ced82399a78260a7f34a7a11)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8019]
Added new descriptions for five kernel variables and two tasks.
(From yocto-docs rev: 834aebb75dce1c905b1e0f142d0d7de6bb44e7d4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8375]
Applied some suggested simpler wording for this bulleted item
of information. Also, did some paragraph editing for better
organization.
(From yocto-docs rev: fd3e277b01ed6fd3580a1c008b1ac05bcfb98f38)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Running oe-selftest requires some Python packages for all
the supported distros. I added new sections in there to cover
these requirements.
Fixes [YOCTO #8290]
(From yocto-docs rev: a8654267405df9ffb2f4d59d3de4a7eb3653893e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8368]
Apparently there is confusion on how to build a cross-toolchain
using Eclipse and the Yocto plug-in. Specifically on setting
the MACHINE variable, the bblayers.conf stuff, and the
preferences in Eclipse to find things. I added a couple key
things to the section that describes using the OpenEmbedded
build system to build out the toolchain.
(From yocto-docs rev: 68c399e2560600cb3a5951c93d51e2cf1f610ff9)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found four occurances of "1.8" used in manual. These needed
to be set to "&DISTRO;" so that they resolve to the latest
YP release.
(From yocto-docs rev: 9db8a2a04085623588e51740a45ee58c500649f6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj
Costin Constantin
Ed Bartosh
Markus Lehtonen
Dmitry Eremin-Solenikov
Bruce Ashfield
Richard Purdie
Andre Draszik
California Sullivan
Scott Rifenbark
John Maxin
Maciej Borzecki