How do I - Revision history

Simonew: Fix syntax

2023-12-27T18:34:30Z

Fix syntax

← Older revision		Revision as of 18:34, 27 December 2023
Line 129:		Line 129:
	:The conf/local.conf file needs to have the parallel processing lines edited to speed up the baking on multicore systems. I can do that by uncommenting the BB_NUMBER_THREADS and PARALLEL_MAKE variables. Generally, I would set them equal to twice the number of cores used by my host machine. By default, the MACHINE variable is set to qemux86 and for this example is fine. I need to add a line to include the hello package I am building into the image by adding the following line:		:The conf/local.conf file needs to have the parallel processing lines edited to speed up the baking on multicore systems. I can do that by uncommenting the BB_NUMBER_THREADS and PARALLEL_MAKE variables. Generally, I would set them equal to twice the number of cores used by my host machine. By default, the MACHINE variable is set to qemux86 and for this example is fine. I need to add a line to include the hello package I am building into the image by adding the following line:

	~~IMAGE_INSTALL_append~~ = " hello"		IMAGE_INSTALL:append = " hello"

	;Step Seven		;Step Seven
Line 141:		Line 141:
	;Step Nine		;Step Nine
	:Once the emulator comes up, login as root with no password. Then, at the prompt, enter "hello" to run your application.		:Once the emulator comes up, login as root with no password. Then, at the prompt, enter "hello" to run your application.



	==Q: How do I setup Intel® Atom™ Processor E6xx based system for media playback? ==		==Q: How do I setup Intel® Atom™ Processor E6xx based system for media playback? ==

Simonew: Update fpr new cve check api

2023-12-27T16:07:08Z

Update fpr new cve check api

← Older revision		Revision as of 16:07, 27 December 2023
Line 230:		Line 230:

	==Q: How do I get a list of CVEs patched? ==		==Q: How do I get a list of CVEs patched? ==
	'''A:''' cve-check ~~tool~~ is available from 2.2 release (~~poky/~~meta/recipes-~~devtools~~/cve-check~~-tool~~)		'''A:''' cve-check is available from 2.2 release (meta/recipes-core/meta/cve-update-nvd2-native.bb is used for acessing the new NVD database 2.0 API, meta/classes/cve-check.bbclass implements the check of recipes against CVEs).


	To run it just inherit the class in conf/local.conf file:		To run it just inherit the class in conf/local.conf file:
Line 236:		Line 237:
	# INHERIT += "cve-check"		# INHERIT += "cve-check"

	~~Source and run~~:		Examples:
	# bitbake -c cve_check openssl
			1. To check for CVEs in openssl
			# bitbake -c cve_check openssl

			2. To check for all recipes build for core-image-sato
	# bitbake core-image-sato		# bitbake core-image-sato
	# bitbake -k -c cve_check universe		# bitbake -k -c cve_check universe


	Log files are created under		Log files are created under tmp/log/cve/
	~~unzip~~/~~1_6.0-r5~~/cve/~~cve~~.~~log~~		...
	~~gnutls/3~~.~~5.3~~-~~r0/cve/cve~~.~~log~~		libmicrohttpd_cve.json
	~~glibc/2~~.24-~~r0/cve/cve~~.~~log~~		libmicrohttpd-native_cve.json
	~~glibc~~-~~initial/2.24~~-~~r0/cve/cve~~.~~log~~		libmnl_cve.json
			libmnl-native_cve.json
			libmodule-build-perl_cve.json
	...		...

	Example of log file:		Example of log file:
	~~PACKAGE NAME~~: ~~perl~~
	~~PACKAGE VERSION~~: 5.~~22.1~~		{
	~~CVE~~: CVE-~~2016~~-~~1238~~		"version": "1",
	~~CVE STATUS~~: ~~Patched~~		"package": [
	~~CVE SUMMARY:~~ ....		{
	~~...~~.		"name": "zstd",
	~~CVSS v2 BASE SCORE~~: ~~7.2~~		"layer": "meta",
	~~VECTOR~~: ~~LOCAL~~		"version": "1.5.5",
	~~MORE INFORMATION~~: https://~~web.~~nvd.nist.gov~~/view~~/vuln/detail~~?vulnId=~~CVE-~~2016~~-~~1238~~		"products": [
			{
			"product": "zstandard",
			"cvesInRecord": "Yes"
			}
			],
			"issue": [
			{
			"id": "CVE-2019-11922",
			"summary": "A race condition in the one-pass compression functions of Zstandard prior to version 1.3.8 could allow an attacker to write bytes out of bounds if an output buffer smaller than the recommended size was used.",
			"scorev2": "6.8",
			"scorev3": "8.1",
			"vector": "NETWORK",
			"vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P",
			"status": "Patched",
			"link": "https://nvd.nist.gov/vuln/detail/CVE-2019-11922"
			},
			...

	==Q: How do I build a wic image? ==		==Q: How do I build a wic image? ==

Simonew: /* Q: How do I build a wic image? */

2023-12-27T15:29:26Z

Q: How do I build a wic image?

← Older revision		Revision as of 15:29, 27 December 2023
Line 266:		Line 266:
	# bitbake <target-image-type>		# bitbake <target-image-type>

	The resulting images (*.wic) will be present in the "tmp/deploy/images" folder		The resulting images (*.wic) will be present in the "tmp/deploy/images" folder. E.g. if you build for core-image-minimal for qemzx86-64 you should find a file like: core-image-minimal-qemux86-64.rootfs.wic

Jeremiah: Added requirement to add gplv2 libs when screening for gplv3 at build time

2017-11-29T15:00:32Z

Added requirement to add gplv2 libs when screening for gplv3 at build time

← Older revision		Revision as of 15:00, 29 November 2017
Line 212:		Line 212:

	==Q: How do I build an image without GPLv3 Licensed packages ? ==		==Q: How do I build an image without GPLv3 Licensed packages ? ==
	'''A:''' Add ~~this~~ line 'INCOMPATIBLE_LICENSE = "GPLv3"' in your <code>conf/local.conf</code> :		'''A:''' Add the line 'INCOMPATIBLE_LICENSE = "GPLv3"' in your <code>conf/local.conf</code> and ensure you have the GPLv2 replacement libraries. (Caveat emptor; they are not as well maintained.) From the Yocto Mega-Manual 2.4;

			"If you use INCOMPATIBLE_LICENSE to exclude GPLv3 or set PREFERRED_VERSION to substitute a GPLv2 version of a GPLv3 recipe, then you must add the meta-gplv2 layer to your configuration."

	Then, build the image:		Then, build the image:

Tom Rini: /* Q: How do I create my own source download mirror ? */ Make it clear we need file URI + /path/to/source/mirror

2017-11-10T01:18:05Z

Q: How do I create my own source download mirror ?: Make it clear we need file URI + /path/to/source/mirror

← Older revision		Revision as of 01:18, 10 November 2017
Line 8:		Line 8:
	Make a complete build with these variables set in your <code>conf/local.conf</code>:		Make a complete build with these variables set in your <code>conf/local.conf</code>:

	SOURCE_MIRROR_URL ?= "file://source_mirror/sources/"		SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
	INHERIT += "own-mirrors"		INHERIT += "own-mirrors"
	BB_GENERATE_MIRROR_TARBALLS = "1"		BB_GENERATE_MIRROR_TARBALLS = "1"
Line 14:		Line 14:
	After a complete build, copy all files (not symlinks) in your download directory to the desired source mirror directory. Test by setting the variables below in <code>conf/local.conf</code>:		After a complete build, copy all files (not symlinks) in your download directory to the desired source mirror directory. Test by setting the variables below in <code>conf/local.conf</code>:

	SOURCE_MIRROR_URL ?= "file://source_mirror/sources/"		SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
	INHERIT += "own-mirrors"		INHERIT += "own-mirrors"
	BB_GENERATE_MIRROR_TARBALLS = "1"		BB_GENERATE_MIRROR_TARBALLS = "1"

Rebecca Chang Swee Fun: Added Q&A on how to build wic image

2017-11-09T08:29:35Z

Added Q&A on how to build wic image

← Older revision		Revision as of 08:29, 9 November 2017
Line 257:		Line 257:
	VECTOR: LOCAL		VECTOR: LOCAL
	MORE INFORMATION: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1238		MORE INFORMATION: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1238

			==Q: How do I build a wic image? ==
			'''A:''' Append "wic" to IMAGE_FSTYPES in your <code>conf/local.conf</code> :

			Then, build the target image type as usual:
			# bitbake <target-image-type>

			The resulting images (*.wic) will be present in the "tmp/deploy/images" folder

SonaSarmadi at 09:01, 28 October 2016

2016-10-28T09:01:35Z

← Older revision		Revision as of 09:01, 28 October 2016
Line 228:		Line 228:

	==Q: How do I get a list of CVEs patched? ==		==Q: How do I get a list of CVEs patched? ==
	'''A:''' > cve-check tool is available from 2.2 release (poky/meta/recipes-devtools/cve-check-tool)		'''A:''' cve-check tool is available from 2.2 release (poky/meta/recipes-devtools/cve-check-tool)

	To run it just inherit the class in conf/local.conf file:		To run it just inherit the class in conf/local.conf file:

	INHERIT += "cve-check"		# INHERIT += "cve-check"

	Source and run		Source and run:
	# bitbake -c cve_check openssl		# bitbake -c cve_check openssl
	# bitbake core-image-sato		# bitbake core-image-sato
	# bitbake -k -c cve_check universe		# bitbake -k -c cve_check universe

	~~EX:~~
	~~bitbake -k -c cve_check universe~~

	~~log~~ files are created under		Log files are created under
	unzip/1_6.0-r5/cve/cve.log		unzip/1_6.0-r5/cve/cve.log
	gnutls/3.5.3-r0/cve/cve.log		gnutls/3.5.3-r0/cve/cve.log
	glibc/2.24-r0/cve/cve.log		glibc/2.24-r0/cve/cve.log
	glibc-initial/2.24-r0/cve/cve.log		glibc-initial/2.24-r0/cve/cve.log
	~~foomatic-filters/4.0.17-r1/cve/cve.log~~		...
	~~bzip2/1.0.6-r5/cve/cve.log~~
	~~libxml2/2.9.4-r0/cve/cve.log~~
	....

	Example of log file:		Example of log file:
	PACKAGE NAME: perl		PACKAGE NAME: perl
	PACKAGE VERSION: 5.22.1		PACKAGE VERSION: 5.22.1
	CVE: CVE-2016-1238		CVE: CVE-2016-1238
	CVE STATUS: Patched		CVE STATUS: Patched
	CVE SUMMARY: ....		CVE SUMMARY: ....
	....		....
	CVSS v2 BASE SCORE: 7.2		CVSS v2 BASE SCORE: 7.2
	VECTOR: LOCAL		VECTOR: LOCAL
	MORE INFORMATION: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1238		MORE INFORMATION: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1238

SonaSarmadi at 08:53, 28 October 2016

2016-10-28T08:53:38Z

← Older revision		Revision as of 08:53, 28 October 2016
Line 226:		Line 226:

	If those versions are same, then we have the latest upstream version of package		If those versions are same, then we have the latest upstream version of package

			==Q: How do I get a list of CVEs patched? ==
			'''A:''' > cve-check tool is available from 2.2 release (poky/meta/recipes-devtools/cve-check-tool)

			To run it just inherit the class in conf/local.conf file:

			INHERIT += "cve-check"

			Source and run
			# bitbake -c cve_check openssl
			# bitbake core-image-sato
			# bitbake -k -c cve_check universe

			EX:
			bitbake -k -c cve_check universe

			log files are created under
			unzip/1_6.0-r5/cve/cve.log
			gnutls/3.5.3-r0/cve/cve.log
			glibc/2.24-r0/cve/cve.log
			glibc-initial/2.24-r0/cve/cve.log
			foomatic-filters/4.0.17-r1/cve/cve.log
			bzip2/1.0.6-r5/cve/cve.log
			libxml2/2.9.4-r0/cve/cve.log
			....

			Example of log file:
			PACKAGE NAME: perl
			PACKAGE VERSION: 5.22.1
			CVE: CVE-2016-1238
			CVE STATUS: Patched
			CVE SUMMARY: ....
			....
			CVSS v2 BASE SCORE: 7.2
			VECTOR: LOCAL
			MORE INFORMATION: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1238

Maxin B. John: document checkpkg task find the latest upstream version

2016-02-17T14:20:01Z

document checkpkg task find the latest upstream version

← Older revision		Revision as of 14:20, 17 February 2016
Line 216:		Line 216:
	Then, build the image:		Then, build the image:
	# bitbake <image-name>		# bitbake <image-name>

			==Q: How do I ensure that I am using the latest upstream version of the package? ==
			'''A:''' Add this line 'INHERIT += "distrodata"' in your <code>conf/local.conf</code> :

			After that, run this command in the build directory:
			# bitbake -c checkpkg <package>
			Then, check the 'Version' and 'Upver' fields in the below listed file:
			# gedit tmp/log/checkpkg.csv

			If those versions are same, then we have the latest upstream version of package

Maxin B. John: INCOMPATIBLE_LICENSE = "GPLv3" info

2015-08-25T13:52:19Z

INCOMPATIBLE_LICENSE = "GPLv3" info

← Older revision		Revision as of 13:52, 25 August 2015
Line 210:		Line 210:
	Yocto_Build_Appliance.vmx		Yocto_Build_Appliance.vmx
	Yocto_Build_Appliance.vmxf		Yocto_Build_Appliance.vmxf

			==Q: How do I build an image without GPLv3 Licensed packages ? ==
			'''A:''' Add this line 'INCOMPATIBLE_LICENSE = "GPLv3"' in your <code>conf/local.conf</code> :

			Then, build the image:
			# bitbake <image-name>