Bumping the linux-yocto 3.19 SRCREVs to integrate the 3.19.5 korg
stable updates, as well as the following meta data changes:
205aca0c1241 meta: intel-common: Enable USB-based Bluetooth hardware
b6a810e8e808 meta: features/bluetooth: add support for USB Bluetooth hardware
767f3fa34680 common-pc-drivers: Add CONFIG_EEPROM_AT24
e308b2c52519 intel-core*: Add Braswell soc support
8c1c74d5052b braswell: Add features/soc/braswell
(From OE-Core rev: 2b163b8bbe8363e24f951ec507691ac692bc80b0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes affecting future time stamps
Egypt will not observe DST in 2015 and will consider canceling it
permanently. For now, assume no DST indefinitely.
(Thanks to Ahmed Nazmy and Tim Parenti.)
Changes affecting past time stamps
America/Whitehorse switched from UTC-9 to UTC-8 on 1967-05-28, not
1966-07-01. Also, Yukon's time zone history is documented better.
(Thanks to Brian Inglis and Dennis Ferguson.)
Change affecting past and future time zone abbreviations
The abbreviations for Hawaii-Aleutian standard and daylight times
have been changed from HAST/HADT to HST/HDT, as per US Government
Printing Office style. This affects only America/Adak since 1983,
as America/Honolulu was already using the new style.
(From OE-Core rev: b9f366ab4e0a9cad69b631f402b9afa02d40f667)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kill 2 bugs with one patch
| insserv.c:997:5: note: each undeclared identifier is reported only
once for each function it appears in
| insserv.c:997:15: error: expected ';' before 'char'
| extension char buf[strlen(myname)+2+strlen(fmt)+1];
| ^
| insserv.c: In function 'main':
| insserv.c:2379:5: error: 'extension' undeclared (first use in this
function)
| extension char * argr[argc];
| ^
| insserv.c:2379:15: error: expected ';' before 'char'
| extension char * argr[argc];
| ^
| insserv.c:2401:2: error: 'argr' undeclared (first use in this
function)
| argr[c] = (char*)0;
| ^
Change-Id: I36b7fb9e8baeda5a7cc252da10c0527401248226
(From OE-Core rev: c0f074714e34145dd6cdac6df5c325fdce649f01)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
LIC_FILES_CHKSUM change is due to shifting of
the hunk to different line numbers, checksum remains same still
Change-Id: I0ce0cc96d39c801e57394f7a839a01d11a6f3979
(From OE-Core rev: 87749a627d0d34f7338ecc55a377a273c66562f3)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0.28 was released 2 years ago and bunch of patches
have gone in since. The commit rate is quite low
so its not a lot of churn to use. We have backports
for few bugs that are removed. Git version of recipe is removed too
since its no longer needed
Change-Id: I4b57db15320c76b1de5d26a733e60436663ff34a
(From OE-Core rev: c7478e328f6507350b7d2d2c790b3dd2bfe2d832)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gcc-5 is stricter and complains about const to non-const
conversions, we backport the patch from upstream into 2.00
Change-Id: I17db365fdd253daaa1ab726e2a70ecad0ac7b2ae
(From OE-Core rev: 7d79a7bfffbc39090b22bb7696cc5dbc832e49b6)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is turned on by default in gcc-5 so far
we have been getting by this issue but time to fix it
has now come
Change-Id: I012248731de0be7a9b7e232073746360fe6c83dd
(From OE-Core rev: 8d8db821d7bcf30079f5a71c255481b12ec00e17)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
see https://gcc.gnu.org/gcc-5/porting_to.html
we need to stop the preprocessor from generating the #line directives
or we run into issues like
| checking for apr_int64_t Python/C API format string...
| configure: error: failed to recognize APR_INT64_T_FMT on this platform
| Configure failed. The contents of all config.log files follows to aid
debugging
| ERROR: oe_runconf failed
Rightly subversion should be fixed but lets leave that to subversion
folks
Change-Id: I02a89798ff949f79967ab0a73adcddaa4218662d
(From OE-Core rev: 7793b1c425077ed6ed11a9bc2a8b1b96612b1c96)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will ensure that compiler does not initialize the definitions
in header files
Change-Id: I1076201c667f96707c320a51a77d4a70e22df750
(From OE-Core rev: 2e9a4198fc9a9fcc78eddb6cd5c2ad51a2e8d3e7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With gcc-5 defaulting to gnu11 C we need to follow
c99 inline semantics
Change-Id: I397520c36c81634556b3f3782aebc532e4a79aed
(From OE-Core rev: 944f94a32577969ee1fc197ab285b0abd9e541fa)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport a patch from fedora details are in patch header
Change-Id: I6b8dfaae3b751071bf8b0d88b15a4f95c19877f6
(From OE-Core rev: 100ab2578bd2025aed940fddce467a4606962695)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Make skipping expression simpler to check for given libc
Make sure glibc specific items are covered with right override
Change-Id: I8b4a0b7cbfe38ffdc9320f798038c79c7220552b
(From OE-Core rev: 6f4be55ca66b4470aa46c0ae356070ed166f44ce)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* modify gtk-option patch so it's for configure.ac and not
configure.in
(From OE-Core rev: 25b4cac50ba05a8faeb3b2013253103b98e5f533)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Using PERLHOSTLIB as possible, which is same as
${STAGING_LIBDIR_NATIVE}/perl-native/perl/${@get_perl_version(d)}
(From OE-Core rev: 981a054eb352bcdcc2b9450dc24718e6695ac99f)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The upstream systemd git repo only contains the main systemd branch that
progresses at a quick pace, continuously bringing both bugfixes and new features.
Distributions usually prefer basing their releases on stabilized versions
that receive the bugfixes but not the features.
(From OE-Core rev: c21bf9d7bb0cb90392ed50a44c57a3d068b88ef9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oe-selftest --list-classes crashes because
of a bad indent (see below). Fixed.
systemd-build$ oe-selftest --list-classes
2015-04-22 12:12:39,141 - selftest - INFO - Listing all available test modules:
_sstatetests_noauto (hidden)
-- SStateBase
-- RebuildFromSState
-- -- test_sstate_rebuild
-- -- test_sstate_relocation
_toaster (hidden)
Traceback (most recent call last):
File "/mnt/Yo/yoctoproject/poky/scripts/oe-selftest", line 201, in <module>
ret = main()
File "/mnt/Yo/yoctoproject/poky/scripts/oe-selftest", line 157, in main
modlib = importlib.import_module(test)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/mnt/Yo/yoctoproject/poky/meta/lib/oeqa/selftest/_toaster.py", line 438
time.sleep(3)
^
IndentationError: unexpected indent
(From OE-Core rev: 46869abf72c1c5babce49537f221d7a4f53ca820)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
`bitbake uninative-tarball' raises the following warning.
WARNING: Function doesn't exist
This is because SDK_PACKAGING_FUNC is set to "" in its recipe.
Anyway, we need to check this variable to avoid executing empty function.
[YOCTO #7598]
(From OE-Core rev: 4c0ae7cce06de15f6881654ecec7f8bb743ff389)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This task is meaningless for uninative-tarball as the package task
has been deleted. Besides, sometimes it would cause problems. To
reproduce, use the following command.
bitbake uninative-tarball -c cleansstate && bitbake uninative-tarball &&
bitbake uninative-tarball -c clean && bitbake uninative-tarball
The error is something like below.
File: 'sstate.bbclass', lineno: 33, function: sstate_installpkg
0029: bb.build.exec_func(f, d)
0030:
0031: for state in ss['dirs']:
0032: prepdir(state[1])
*** 0033: os.rename(sstateinst + state[0], state[1])
0034: sstate_install(ss, d)
0035:
0036: for plain in ss['plaindirs']:
0037: workdir = d.getVar('WORKDIR', True)
Exception: OSError: [Errno 2] No such file or directory
[YOCTO #7597]
(From OE-Core rev: 8f905077aaed3dbeeed04787add1cf725fa87bdc)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GNOME Mobile no longer applies. I updated text to use the
GTK+ wordings.
(From yocto-docs rev: 09e67479f470ca4b21f532c5fc96f36d3bf1a39d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I typically try to use the underscore character to string together
multi-word user-input descriptors in examples. I fixed a bunche
here.
(From yocto-docs rev: 68474b5a8b5c96b0fc19fda29e667369f4606e31)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the introduction, the ref-manual references several other YP
manuals. If the manual is build separately, these references resolve
to the appropriate manuals. When the mega-manual is built, the
same references are designed to not become links. In otherwords,
mega-manual.sed processes those links out. This is by design.
I found a #profile-manual tag on one of the links in the introduction.
This resulted in a link in the mega-manual that would go nowhere. I
removed the tag.
(From yocto-docs rev: fdaf114ece20994ec55061612ab53e9334afde26)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A link was going to an old YP page that talked about patch
style guide stuff. That page simply redirects the user to a
styleguide of the OE. I fixed the link in the manual to go
directly to that page now.
(From yocto-docs rev: 913c30eae42e89cc6f8dd99026594c2843985c58)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found a link that is processed by the mega-manual.sed file correctly
but for the situation it does not resolve right. The link is a
"naked" link. In other words, it doesn't have a #<tag> part.
When the .sed file sees these types of links, no hyperlink is
generated. I found a case in the dev-manual where I reference the
Toaster Manual in general and would like a link that would take the
user there. So, I had to add a #<tag> part to the link in the XML
(From yocto-docs rev: ab11e9822b5ec1b0f7138f1419ce9c340f6f27ad)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I put this in the intro list for the section that presents various
ways to use YP.
(From yocto-docs rev: 05f924f799a1f1396bf7154b298aabc3d06ad1d7)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This practice is not good. I had one in the manual. I reworded
the text to not use that term in a link.
(From yocto-docs rev: 53636ae7370827945b31d11785410dd44670bb91)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Repositories, Tags, and Branches" section had some wording
that described how branches are maintained in the poky repo that
made it hard to maintain in the doc from release to release. I had
a list of past releases by name and as such would have to update
it every release to make it reflect the last set. Well... this
is not the best way to do this and proved out as it slipped through
the cracks for the YP 1.8 release. Consequently, I recast the text
so it is "release proof".
(From yocto-docs rev: b6e27d06df58a43bb767e9616ccf3c0711e83cf6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In an attempt to keep the project as much open source as possible,
I removed the link to Intel from this list of resources. We don't
list Linux, OpenedHand, Wind River, etc.
(From yocto-docs rev: 5efe375a94a14d4a70aa2c3ff9ab39d6c7362526)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some stuff about "poky" meaning the default distribution
when using YP and the poky git repository to build an image.
(From yocto-docs rev: bd534a5bdf405044c8f1a60ee9e251bff2a0e53c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The send-error-report tool syntax has slightly changed since the
documentation was written. Removed the [server] part of the
command and added more detail on its use and results.
Reported-by: Michael Wood <michael.g.wood@intel.com>
(From yocto-docs rev: 10e28ab877b327301be536e5d515d5a419d082ac)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Wic is not using parted and other runtime dependencies from host
system anymore. It uses native tools instead. Removed host parted
from the list of requirements. Added instructions to build native
tools.
(From yocto-docs rev: ab22aff62bd9ffde3dfefe9fcabadc6e5aae7e31)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
An old note still existed in this entry that stated we don't support
glibc. This is not true. I deleted the note.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: e72f248f45678fb445e60106dd338c4d9cd114d8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #7630]
Apparently the text relocation being done here can cause runtime
performance issues. I documented a potential work-around for the
issue and provided a cross-reference link to an external site for
more general information about text relocation at runtime.
Reported-by: Laszlo Papp <lpapp@kde.org>
(From yocto-docs rev: f7ba2fd03ee40c5dbe6a07a24a63d9147857ed78)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
