summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ref-manual, dev-manual: Clean up of a commitScott Rifenbark2019-10-232-11/+16
| | | | | | | | | | | | | Alejandro Enedino Hernandez Samaniego <aehs29@gmail.com> commited a change to these manuals (see 9e79e96cad66316c1b4ee608723edfa763f0f9ef) and did not use YP documentation standards for the content. I cleaned up the text and tabbing. (From yocto-docs rev: 9c95799322e1830a5faae0980384ab10b6504007) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Removed deprecated link to ref-classes-bluetoothScott Rifenbark2019-10-231-4/+3
| | | | | | | | | This was in a moving to YP version 1.8 migration section. (From yocto-docs rev: b87f0882c39524747004fafc4d1caf58b3344c3a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documenation: Changed "2.8" to "3.0".Scott Rifenbark2019-10-2311-45/+45
| | | | | | | | | | I was using "2.8" throughout the manual set instead of "3.0". Updated all aspects to "3.0". (From yocto-docs rev: db19937e98c59d4d2a9ce89877be3c8e0b05991a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: 2nd pass 3.0 migrationScott Rifenbark2019-10-231-11/+11
| | | | | | | | | | Turned "2.8" into "3.0". Nobody told me about skipping 2.8 and 2.9. (From yocto-docs rev: 13819f0651c48adae9d1a8d6d19341ba5ee44978) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Added info to "Selecting an Initialization Manager"Scott Rifenbark2019-10-231-0/+41
| | | | | | | (From yocto-docs rev: c402ebcb51b6400d79c62ff44aeae57db982565e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Updated the release date to October 2019Scott Rifenbark2019-10-231-1/+1
| | | | | | | (From yocto-docs rev: 21042fd8ad463c996e554f52359a599ee7d35c12) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: First pass of 2.8 migration changes (WIP)Scott Rifenbark2019-10-231-0/+98
| | | | | | | (From yocto-docs rev: 2c0f6cd921132caa4f49c34ac592db68be27761a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: mark connman-wait-online as SYSTEMD_PACKAGEAndré Draszik2019-10-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The connman-wait-online package currently isn't marked as systemd-enabled package. This means it is impossible to auto-enable the service during image creation or package installation, as no preset files and no pkg_postinst() snippet is being created. This change should have been done as part of the upgrade to v1.31 Note: connman-wait-online is needed when connman is in use in more complex network/interface setups for systemd's network-online.target to report success. systemd-networkd's systemd-networkd-wait-online.service alone doesn't work in such scenarios and simply times out, as it know nothing about the expected network/ interface configuration, meaning the target doesn't boot successfully (systemctl list-units --failed), and long delays are seen, caused by waiting for the systemd-networkd-wait-online.service timeout. (From OE-Core rev: 1a8d18eeee6dc188d8becc778bfa933031490781) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-devicetree: Cope with non-standard kernel deploy subdirectoryMike Crowe2019-10-231-10/+10
| | | | | | | | | | | | | | | | kernel.bbclass installs non-standard kernels (where KERNEL_PACKAGE_NAME is not "kernel") in a subdirectory of ${DEPLOYDIR}. To achieve this kernel_do_deploy sets the deployDir shell variable to ${DEPLOYDIR} for the standard kernel or ${DEPLOYDIR}/${KERNEL_DEPLOYSUBDIR} for non-standard kernels. kernel-devicetree.bbclass's do_deploy_append ought to do the same and can do so by using the same shell variable. (From OE-Core rev: db5752911fe085337b9d3d4af85f89a0c664388e) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-fitimage: Cope with non-standard kernel deploy subdirectoryMike Crowe2019-10-231-9/+9
| | | | | | | | | | | | | | | | kernel.bbclass installs non-standard kernels (where KERNEL_PACKAGE_NAME is not "kernel") in a subdirectory of ${DEPLOYDIR}. To achieve this kernel_do_deploy sets the deployDir shell variable to ${DEPLOYDIR} for the standard kernel or ${DEPLOYDIR}/${KERNEL_DEPLOYSUBDIR} for non-standard kernels. kernel-fitimage.bbclass's kernel_do_deploy_append ought to do the same and can do so by using the same shell variable. (From OE-Core rev: d324b22d32eaea9e4337c963c8b1a33b0ba6a2dd) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic/engine: use 'linux-swap' for swap file systemChee Yang Lee2019-10-231-1/+1
| | | | | | | | | | | | | | [YOCTO #13312] see https://bugzilla.yoctoproject.org/show_bug.cgi?id=13312 wic/engine.Disk._get_part_image was looking at variable fstypes for supported fstype which is 'swap' but image build with 'linux-swap'. supported fstype should be 'linux-swap'. (From OE-Core rev: 7e6da22fe4faf841bcec02e55f376b4dae04d6a8) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic/help: change 'wic write' help descriptionChee Yang Lee2019-10-231-2/+2
| | | | | | | | | | | | | update the help desciption for 'wic write' command to match behaviour. see commit: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/scripts/wic?id=74b44e59be89c738f702948f9e16e367c0ba43ba (From OE-Core rev: 521942bde1d49d987c85bf071275e8e7150d012a) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: fix CVE-2019-16276Chen Qi2019-10-232-0/+164
| | | | | | | (From OE-Core rev: e31f87e289dfd3bbca961e927447a9c7ba816d3f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adwaita-icon-theme: upgrade 3.32.0 -> 3.34.0Andreas Müller2019-10-232-3/+3
| | | | | | | (From OE-Core rev: b4e9af206623755651753ed1b776cedb004e59fd) Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: fix CVE-2019-14287Changqing Li2019-10-233-0/+292
| | | | | | | | | | | | | In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, and can cause incorrect logging, by invoking sudo with a crafted user ID. For example, this allows bypass of !root configuration, and USER= logging, for a "sudo -u \#$((0xffffffff))" command. (From OE-Core rev: 4e11cd561f2bdaa6807cf02ee7c9870881826308) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: Backport fix to assist meta-oe breakageRichard Purdie2019-10-232-0/+96
| | | | | | | | | Add a backported commit from upstream which helps fix build failures in meta-oe. (From OE-Core rev: 6665e84bfba43cd8897b9561b14975ac524fbbe2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap-ng:upgrade 0.7.9 -> 0.7.10Zang Ruochen2019-10-233-3/+3
| | | | | | | (From OE-Core rev: 1d5ab1936c9fdf5d2613562ab1ace920089de49b) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: fix PKNAME name is NULL when use lsblk [LIN1019-2963]Liwei Song2019-10-232-0/+37
| | | | | | | | | | PKNAME is NULL when run "lsblk -o+PKNAME /dev/sda1" backport an upstream patch to fix it. (From OE-Core rev: a5a987ff5e5e333e28be44a12e729907272ea3cb) Signed-off-by: Liwei Song <liwei.song@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-setuptools:upgrade 41.2.0 -> 41.4.0Zang Ruochen2019-10-233-2/+2
| | | | | | | (From OE-Core rev: c94bb5b7431af8b495a3fa96e96d968dc45fb4f3) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip:upgrade 19.2.3 -> 19.3.1Zang Ruochen2019-10-231-2/+2
| | | | | | | (From OE-Core rev: 0f3fe0edb5a7c26d4a3162d54c9e627e396af476) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/context.py: ignore more files when loading controllersAndré Draszik2019-10-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When loading controllers as (external) modules, the code currently tries to load all files ending with .py. This is a problem when during development using an editor that creates a lock-file in the same directory as the .py file, as the lock file is typically called '.#xxxx.py'. Python will try to load the lock file and fail miserably with an exception: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module> 0001: *** 0002:do_testimage(d) 0003: File: 'poky/meta/classes/testimage.bbclass', lineno: 114, function: do_testimage 0110: netstat -an 0111:} 0112: 0113:python do_testimage() { *** 0114: testimage_main(d) 0115:} 0116: 0117:addtask testimage 0118:do_testimage[nostamp] = "1" File: 'poky/meta/classes/testimage.bbclass', lineno: 294, function: testimage_main 0290: 0291: # the robot dance 0292: target = OERuntimeTestContextExecutor.getTarget( 0293: d.getVar("TEST_TARGET"), logger, d.getVar("TEST_TARGET_IP"), *** 0294: d.getVar("TEST_SERVER_IP"), **target_kwargs) 0295: 0296: # test context 0297: tc = OERuntimeTestContext(td, logger, target, host_dumper, 0298: image_packages, extract_dir) File: 'poky/meta/lib/oeqa/runtime/context.py', lineno: 116, function: getTarget 0112: # XXX: Don't base your targets on this code it will be refactored 0113: # in the near future. 0114: # Custom target module loading 0115: target_modules_path = kwargs.get('target_modules_path', '') *** 0116: controller = OERuntimeTestContextExecutor.getControllerModule(target_type, target_modules_path) 0117: target = controller(logger, target_ip, server_ip, **kwargs) 0118: 0119: return target 0120: File: 'poky/meta/lib/oeqa/runtime/context.py', lineno: 128, function: getControllerModule 0124: # ImportError raised if a provided module can not be imported. 0125: @staticmethod 0126: def getControllerModule(target, target_modules_path): 0127: controllerslist = OERuntimeTestContextExecutor._getControllerModulenames(target_modules_path) *** 0128: controller = OERuntimeTestContextExecutor._loadControllerFromName(target, controllerslist) 0129: return controller 0130: 0131: # Return a list of all python modules in lib/oeqa/controllers for each 0132: # layer in bbpath File: 'poky/meta/lib/oeqa/runtime/context.py', lineno: 163, function: _loadControllerFromName 0159: # Raise ImportError if a provided module can not be imported 0160: @staticmethod 0161: def _loadControllerFromName(target, modulenames): 0162: for name in modulenames: *** 0163: obj = OERuntimeTestContextExecutor._loadControllerFromModule(target, name) 0164: if obj: 0165: return obj 0166: raise AttributeError("Unable to load {0} from available modules: {1}".format(target, str(modulenames))) 0167: File: 'poky/meta/lib/oeqa/runtime/context.py', lineno: 173, function: _loadControllerFromModule 0169: @staticmethod 0170: def _loadControllerFromModule(target, modulename): 0171: obj = None 0172: # import module, allowing it to raise import exception *** 0173: module = __import__(modulename, globals(), locals(), [target]) 0174: # look for target class in the module, catching any exceptions as it 0175: # is valid that a module may not have the target class. 0176: try: 0177: obj = getattr(module, target) Exception: ImportError: No module named 'oeqa.controllers.' Simply ignore those when collecting the list of files to try to load. (From OE-Core rev: 682f223cf2e2dabe8cf60634b6779bb2d5e359bd) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-package.bbclass: Use with to manage filehandle in do_spit_gconvsOla x Nilsson2019-10-231-8/+7
| | | | | | | | | | Tweak the write loop slightly to avoid dict lookups that can easily be done in the for loop. (From OE-Core rev: 35c65b7336c52c19810e3e9e87a36a8636ac4120) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool-source.bbclass: Use with to manage file handle lifetimeOla x Nilsson2019-10-231-5/+3
| | | | | | | | | Replace copy-and-if with a filtering list comprehension. (From OE-Core rev: eb763856be8da854d37c7d4b8e8d645ab1d3fa06) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Use with to manage file handle lifetimesOla x Nilsson2019-10-231-42/+34
| | | | | | | (From OE-Core rev: e90978056c4b49e138b3d422939bf995829ec3b0) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error.bbclass: Use with to control file handle lifetimeOla x Nilsson2019-10-231-6/+2
| | | | | | | (From OE-Core rev: ab108dfc690fb95b66f1c6243ff165f0849fa2b1) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/package_manager: Use with to control file handle lifetimeOla x Nilsson2019-10-231-4/+4
| | | | | | | (From OE-Core rev: e3e86d6683e305865c9fd171c6081aec037d9870) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/packagedata: Use with to control file handle lifetimeOla x Nilsson2019-10-231-3/+2
| | | | | | | (From OE-Core rev: 28b3635b7f40b627a9d6294a78589c78f0c682c8) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe.types.path: Use with to control file handle lifetimeOla x Nilsson2019-10-231-2/+2
| | | | | | | (From OE-Core rev: b6e7fee68d018e5f148a7a02cf110bc210022a72) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/recipetool: Use with to control file handle lifetimeOla x Nilsson2019-10-231-1/+3
| | | | | | | (From OE-Core rev: 890fbd77315474fbd582f8bbeb26925c6a42d8d4) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: add missing Upstream-Status tagsRoss Burton2019-10-232-0/+6
| | | | | | | (From OE-Core rev: 85d9348272c4e6d59977a514338f29fe5156eb2c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xorgproto: upgrade to 2019.2Ross Burton2019-10-231-2/+2
| | | | | | | (From OE-Core rev: e4d3f842194ea1ff584ae4fe8ad211dd3e706e6c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libx11: upgrade to 1.6.9Ross Burton2019-10-234-96/+7
| | | | | | | (From OE-Core rev: a4834fd1e63b825870b6351bedc203c20abb5ead) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxvmc:upgrade 1.0.11 -> 1.0.12Zang Ruochen2019-10-231-2/+2
| | | | | | | | (From OE-Core rev: 5cf224a701dbc3d779099aab55013c66fe587eb9) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xorgproto: fix summaryRoss Burton2019-10-231-1/+1
| | | | | | | (From OE-Core rev: 7346e6d4f584439ed1dc9d228b8bd015da8a6668) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: update dbus-1.init to reflect new PID fileTom Benn2019-10-231-2/+2
| | | | | | | | | | The PID file referenced in dbus-1.init script was out of date and no longer existed. This meant that dbus could not be restarted via init.d without force removing the old PID file. (From OE-Core rev: 2ed6f06f30cb54b9c70f1a92d93c920ec4d01ffe) Signed-off-by: fridgecow <fridgecow@fb.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcrypt: fix CVE-2019-12904Yi Zhao2019-10-234-0/+603
| | | | | | | | | | | | | | | | | | | | | In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.) Reference: https://nvd.nist.gov/vuln/detail/CVE-2019-12904 Patches from: https://github.com/gpg/libgcrypt/commit/1374254c2904ab5b18ba4a890856824a102d4705 https://github.com/gpg/libgcrypt/commit/daedbbb5541cd8ecda1459d3b843ea4d92788762 https://github.com/gpg/libgcrypt/commit/a4c561aab1014c3630bc88faf6f5246fee16b020 (From OE-Core rev: 37e390ff05b6a4509019db358ed496731d80cc51) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Fix CVE-2019-10160Changqing Li2019-10-232-0/+82
| | | | | | | | (From OE-Core rev: b4240b585d7fcac2fdbf33a8e72d48cb732eb696) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: refresh upstreamed patchesRoss Burton2019-10-232-16/+14
| | | | | | | (From OE-Core rev: f217063edd1784811679a384d0d54b34b6b81015) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: use specialist assert* methodsRoss Burton2019-10-233-14/+13
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ruby: some ptest fixesAndré Draszik2019-10-231-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * the (new?) ruby expects some additional compiled libraries to run, so we need to copy them as part of ptest. Fixes errors like: # ruby ./runner.rb ./-ext-/vm/test_at_exit.rb Run options: # Running tests: [1/1] TestVM#test_at_exit = 0.06 s 1) Failure: TestVM#test_at_exit [/usr/lib/ruby/ptest/test/-ext-/vm/test_at_exit.rb:7]: 1. [1/2] Assertion for "stdout" | <["begin", "end"]> expected but was | <[]>. 2. [2/2] Assertion for "stderr" | <[]> expected but was | <["-:1:in `require': cannot load such file -- -test-/vm/at_exit (LoadError)", | "\tfrom -:1:in `<main>'"]>. * the 'erb' test can't find the erb binary, as we're not running this from within the build directory (From OE-Core rev: 158d5285372240f6b3502a6c715a2491e37a3118) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: Export ICECC_CC and friends via wrapper-scriptDouglas Royds via Openembedded-core2019-10-231-12/+20
| | | | | | | | | | | | | | | | | By exporting ICECC_CC, ICECC_CXX, and ICECC_VERSION in a wrapper-script, and putting this wrapper-script in the PATH, the Makefiles generated by CMake or the autotools are able to function correctly outside of bitbake. This provides a convenient developer workflow in which the modify-compile-unittest cycle can happen directly in the ${B} directory. The `rm -f $ICE_PATH/$compiler` line is transitional, and can go at some later date (October 2020 or later, perhaps). (From OE-Core rev: 40d74cb1d0ddce930267e49764cacb263b244091) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ruby: update to v2.6.4André Draszik2019-10-236-54/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Most patches had to be refreshed Note that we can now drop EXTRA_AUTORECONF += "--exclude=aclocal" from the recipe, as ruby upstream now fully supports runnning aclocal: https://github.com/ruby/ruby/pull/1793/commits/df9bf70cd2275a3ddc3108f392214fcc4a9b0859 https://github.com/ruby/ruby/commit/ec43478f34de262ebdd2922c488e265344b489c3 Also note that 'created.rid' is not being installed anymore since v2.6.0 While additional LICENSEs were added to the recipe, they should always have been mentioned in this recipe, i.e. the license checksum was updated only because: * URLs were updated * new imported components were mentioned (with no new licenses) * formatting was changed * dates were updated (From OE-Core rev: 7124051b3b2e91e81c7b8565104ae9c5bea10be1) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: make OPENSSL_ENGINES match install pathGeorge McCollister2019-10-231-1/+1
| | | | | | | | | | Set OPENSSL_ENGINES to the path where engines are actually installed. (From OE-Core rev: 59565fec0b3f3e24eb01c03b671913599cd3134d) Signed-off-by: George McCollister <george.mccollister@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs:upgrade 1.45.3 -> 1.45.4Zang Ruochen2019-10-231-1/+1
| | | | | | | | (From OE-Core rev: 87d4e40297ed5469492806d9e7caa605081a8822) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: add ssh key option to deploy-target paramEduardo Abinader2019-10-231-0/+8
| | | | | | | | (From OE-Core rev: 729da1414098c2dd103d9749cf39117881cafeec) Signed-off-by: Eduardo Abinader <eduardoabinader@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ell: update to 0.23Oleksandr Kravchuk2019-10-231-2/+2
| | | | | | | | | | | Changelog: - Add support for checking if uintset is empty. (From OE-Core rev: 649d8db2fb47d8c3c844013210cda8a01f85f54c) Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake.bbclass: add HOSTTOOLS_DIR to CMAKE_FIND_ROOT_PATHMichael Ho2019-10-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | | The find_program command will fail if it is used on a tool that is listed in ASSUME_PROVIDED. This is because these tools are in the hosttools directory which is not listed in CMAKE_FIND_ROOT_PATH so cmake will not find them. Adding the directory HOSTTOOLS_DIR to the CMAKE_FIND_ROOT_PATH variable fixes the initial issue of needing to search for tools in ASSUME_PROVIDED. Note that this change alone does not fix the issue because find_program will by default only look into the subdirectories bin and usr/bin under the paths in CMAKE_FIND_ROOT_PATH to find the programs and the hosttools directory has instead the symlinks directly present without these subdirectories. Set CMAKE_PROGRAM_PATH to by default include the root directory so find_program can search the hosttools directory without needing the prefix directories. (From OE-Core rev: 7847f431cd8db59fce8c9401a603c4b0678ee16d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bison:upgrade 3.4.1 -> 3.4.2Zang Ruochen2019-10-231-2/+2
| | | | | | | | (From OE-Core rev: e44923a61d1631439ec22faf1610989f82544027) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: Add --remove-work option for devtool reset commandSai Hari Chandana Kalluri2019-10-231-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | Enable --remove-work option for devtool reset command that allows user to clean up source directory within workspace. Currently devtool reset command only removes recipes and user is forced to manually remove the sources directory within the workspace before running devtool modify again. Using devtool reset -r or devtool reset --remove-work option, user can cleanup the sources directory along with the recipe instead of manually cleaning it. syntax: devtool reset -r <recipename> Ex: devtool reset -r zip devtool finish -r <recipename> <layer-name> Ex: devtool finish -r zip meta-yocto-bsp (From OE-Core rev: 0d6dd01b8633ad63d77c24568a4b20852aaa366f) Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: ensure that all forms of python3-config are in python3-devRoss Burton2019-10-232-3/+9
| | | | | | | | | | | | | | | | | | | | | | | In multilib builds python3-config gets renamed to eg python3-config-lib64 but this ends up being packaged in python3-core not python3-dev. The manifest uses an extended glob to package all python* binaries that are not python-config into python3-core: "${bindir}/python*[!-config]", However, this doesn't do what was intended, as [] is a range match. Replace the globs with more verbose but precise matches, and clear out FILES_${PN} to ensure that new binaries don't end up in ${PN} (which shouldn't exist). [ YOCTO #13592 ] (From OE-Core rev: c780f21c33b0684dafff3421600cd1c11ddd0c48) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>