O irony: the grub2/gnulib nag macro that says "don't use gets, use fgets" breaks the build if you're using a recent (e)glibc release that has gets removed.
Fedora already #if 0's the check in grub, so I stole their patch.
(From OE-Core master rev: 261e377b08388a288ee521a3629877b89e18e42b)
(From OE-Core rev: 48fb1f19875cac24cb990807523f6e513c7031aa)
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>
Due to some issues with postinstalls that register hooks, we changed the
logic a bit. Now, all postinstalls that register hooks will return
successfully and only after, if hooks fail, mark the package as unpacked.
(From OE-Core master rev: 82dae98d0eb771c05e57635f0f8763b118d8177e)
(From OE-Core rev: 202f1b0e4ee6d912f2bec5991d1cd60bbb0c020e)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will allow to register, in a single postinstall, multiple hooks.
(From OE-Core master rev: b396138ee081c8f5dddbaab0e374787ba2e31029)
(From OE-Core rev: 3daed9c994d3f092caa9cc6e8bab49ab606cb0a2)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will allow to register, in a single postinstall, multiple hooks.
(From OE-Core master rev: 2cd244d6c93ec6d39e2649de64575c365bd4238d)
(From OE-Core rev: 982302219bf5b133f76a0d8213b626f8abef99b3)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will allow to register, in a single postinstall, multiple hooks.
(From OE-Core master rev: 9553874cf02ba443aff1bbead56bacfcda9bb6ca)
(From OE-Core rev: 3ef3b5be29925d8b6579c5bd57e58ce1bced35d8)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Take __BBTASKS, __BBHANDLERS and __BBANONFUNCS into account when
computing the configuration hash.
[YOCTO #4447]
(Bitbake master rev: 260ced7452405fc43ce3d9dd6798236aa07cc716)
(Bitbake rev: 0c744479c2657e433280d9f1884483fa76796b69)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Current if the PR Service fails to start, bitbake carries on regardless or
hangs with no error message. This adds an exception and then handles it correctly
so the UIs correctly handle the error and exit cleanly.
[YOCTO #4010]
(Bitbake master rev: 949c01228a977c3b92bfc0802f6c71b40d8e05b3)
(Bitbake rev: c21c3fd3adc7bbbd7018a03e99f058b05bec10b2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runCommand was returning 'error' but checking for 'err'
resulting in an exception.
(Bitbake master rev: 263aa44ed47e0cb03e1a97e7ed4a50bd9f828c78)
(Bitbake rev: ea7254390807d6d4a34bd07ebe33b381de462ced)
Signed-off-by: Martin Donnelly <martin.donnelly@ge.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
powertop uses gettext during config time and at build time to generate the
messages, so really should inherit gettext.
[YOCTO #4470]
(From OE-Core rev: 8ca272168e3cf9abcab13096a3c4eaadb7e35841)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have
started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until
this can be root-caused and fixed in the kernel, disable paravirtualisation
across all kernels and all qemu machines.
[ YOCTO #4196 ]
(From OE-Core rev: a8c61372b9701bc23b7071499ff2148455d46c84)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The postinstall needs to reference $D, not ${D} which would get expanded
by bitbake. This allows postinsts to run correctly on the target system.
(From OE-Core rev: 6573685a5374034df065c41bbe71c7ac49e4b9a4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we want systemd support we use systemd's udev, so disable systemd
support in this udev to avoid packaging the unit files.
(From OE-Core rev: 36aa37e693bcb76a96761847dbef6a015d96fd98)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libudev previously depended on udev, but this causes problems with multilib
if the user wants to install two variants of libudev as they'll pull in two
variants of udev, which will conflict.
Instead, remove the dependency and rely that the image pulls in udev in some
way, such as the commonly used packagegroup-core-boot.
(From OE-Core rev: 6168ea4e00fd1c8296fe770fa9e2ef00018f5621)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Apparently, the default qemumips color depth was set to 8 and the colors were not
displayed properly. cirrusfb driver doensn't seem to accept color depth
as a kernel parameter, so we have to do it here.
[YOCTO #4340]
(From OE-Core rev: 876e020be334a9350094dbd1a29b9e49eceed603)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The do_populate_lic task has a race with the recipe since it relies on the
kernel being populated in the sysroot. This patch adds in the explicit missing
dependency.
[YOCTO #3534]
(From OE-Core rev: 578937213c6db9fa99981778ce61210e391b19a7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The update-alternatives for multilibs are broken and nothing provides psplash in a
multilib build. This fixes the multilib code.
(From OE-Core rev: db1f6b24ddb2a19fb16b2ebb948bb3274b7ac295)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The postinstall for the opkg run-postinst hook checks for the existence of this
file. We therefore ensure it always exists during image generation.
(From OE-Core rev: 540cf355599e555615ed9684c3b480463588eb78)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
THe USERADD_PARAMS and similar group variables are package specific variables
which should get added to the vardeps of the packaging process. This
change also ensures they get remapped correctly by the multilib code.
(From OE-Core rev: 805add18e7b917aaef61c82c0b5f2e9682af1d0d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we don't do this, multilib packages don't have any code
added to the postinstalls to handle user additions.
(From OE-Core rev: b10d17d1b03fd0564103a6998f218d0968d1032b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otherwise this setting "floats" and leads to non-determinstic builds.
(From OE-Core rev: 4eea01e9d775f2e56958a8bb194aadd8a242946d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the splite of netbase and init-ifupdown, the interfaces file needs to get
moved for the beagleboard
[YOCTO #4334]
(From meta-yocto rev: 8f3ed8620d7df41d30abebd472f0b92933f64fed)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=f76d4b3549ca220fa4bf84db2756ab45e11d06a3
moved volatiles handling for /run to the udev code only. This breaks
sysvinit+systemd combined systems when building sysvinit images.
This patch hacks the udevd init script in systemd to provide
the missing symlink allowing the sysvinit images built with udevd
from systemd to work correctly.
(From OE-Core rev: 6c6e5dc0baccd0904f785b1f80f39b5f530779cf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use ${PN} when specifing service files so that they continue to get packaged
with multilib.
(From OE-Core rev: d394d27b66cbeb4e57017d2a49605243586477ac)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When libdir isn't /lib the files that are in nonarch_base_libdir were being left
out of the -dbg package.
(From OE-Core rev: 60bb2f795a0b3e83de5861185446992fb91ffba0)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previously this was using ${PN}-syslog.service, which changes with multilib.
(From OE-Core rev: ee36f997e68f5a995baf361191cef7a46ff51203)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using multilib this doesn't get caught by the default FILES_${PN}, so add
it.
(From OE-Core rev: 53f1540780e5d4e8035118a1920202735bd0a370)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This effectively reverts the move systemd's libexecdir to /sbin. This caused
too many issues in other places and was not well enough tested this close to
release.
Rather than use base_libdir, the nonarch version is used to try and give some
chance of multilib not being totally broken in the release. Also some variables
are used that mirror the systemd build system to reduce the risk of using
variables that "work" in the general case but will break with multilib.
(From OE-Core rev: e921d43e213f93da176fd27e48b557f802443dec)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently, you can set VIRTUAL-RUNTIME_init_manager to an init system that
isn't in DISTRO_FEATURES. This leads to head scratching over unbootable images.
This adds a sanity check which ensures more valid systems are built.
(From OE-Core rev: c72ec4b52827f75351790eab483d258b2e87611a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This effectively reverts the changes made in b49ddeb11c
to move udev's libexecdir to sbin. The changes caused too many issues in
other places and were not well enough tested this close to a release.
Rather than use base_libdir, the nonarch version is used to try and give some
chance of multilib not being totally broken in the release.
(From OE-Core rev: c50e50fdafad378d75b7b74259a3d55ca0fe3d18)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we put a valid glob like "*/foo/*" into FILES, populate_packages
breaks with a "file exists" message. This is because the glob expansion
does not have "./" prefix however there may already be an entry in
the seen list which does have such a prefix. The easiest/simplest fix
right now is to add the prefix if it doesn't exist which only happens
for certain globs.
(From OE-Core rev: 138c5f3af892e33f576fc7dd268e122b179f82a1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When the mount command is not given the filesystem type to mount, then
it will try all the known filesystems. However, when a filesystem is not
supported by the kernel, the mount function call will return ENODEV.
The following patch, ecd90bc6aa,
introduced a problem because it bailed out on ENODEV too. Instead it should
have only bailed out on ENOMEDIUM.
[YOCTO #4308]
(From OE-Core rev: 82320d2074572477f26887eddc51dc2a1dfea403)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a cross-reference to the section that describes how to
use .bbappend files.
(From yocto-docs rev: 884740c066f0f45cfc85282c6d20737a39d7af88)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section had some problems. It failed to mention the
need to extend FILESPATH by using FILESEXTRAPATHS.
(From yocto-docs rev: e627cf21242a62fb23e93fdae61e8cfce32082a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied some review comments from Paul. Took the warning formatting
out because it sucks.
(From yocto-docs rev: 6c4162777cb686c8b24b15ded2594f4f4a6acba6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added some more clarity about how this variable works and the
implications for using the default setting from the base.bbclass
file. Namely, if you are going to have the build system look
for files in your layer and your layer uses an append file,
then you need to also use the FILESEXTRAPATHS variable to
extend FILESPATHS.
(From yocto-docs rev: 2826fa6f9286efb1d5ca6cf85f65266a35bb8cfc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found it confusing due to not specifically accounting for
.bb and .bbappend files. I added some wording to clearly
specify use given the two types of "recipes". Specifically,
if you are going to use a SRC_URI statment from an append
file, the user really should be aware that they will need
to extend the FILESPATH variable by also using FILESEXTRAPATHS
from within that append file.
(From yocto-docs rev: 8fd0047bd5c4598532afc6f0803f6ae23fa213b2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Further down in the section, a second occurrence of ${FILES}
needed changed.
(From yocto-docs rev: 0212a1ebfef4c5a6a0ae76410f7753bbc41d3e82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was inaccurately referencing the ${FILES} directory when
it should be talking about a "files" directory created in the
user's layer where the kernel .bbappend file resides.
(From yocto-docs rev: 2af3a71db6e6d99b9aa4b710e21f3f3bacff0b82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
