Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-3.0 2021-02-12T23:32:16+00:00 2021-02-12T23:32:16+00:00 Khem Raj raj.khem@gmail.com 2021-02-10T07:40:44+00:00 urn:sha1:fa7db243672ec7d8e1a1f45341ceadb0bc212794 Adding -O can be troublesome in some packages where it may override the O<n> specified by CFLAGS, this can be due to configure processing of CFLAGS and munging them into new values in Makefiles, which is contructed from CC and CFLAGS passed by bitbake environment. Problem arises if the sequence is altered, which seems to be the case in some packages e.g. ncurses, where the value from CC variable is added last and thus overrides -O<n> coming from CFLAGS, Therefore grok the value from SELECTED_OPTIMIZATION and append the appropriate -O<level> flag to lcl_maybe_fortify so the level does not change inaderdantly. Since we do not use -O0 anymore there is no point of checking for DEBUG_BUILD since it uses -Og now which works fine with -D_FORTIFY_SOURCE=2, so check for optlevel O0 instead (From OE-Core rev: 9571a18f7d15b3bffafc2e277ab90a21d6763697) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-10T23:48:55+00:00 akuster akuster808@gmail.com 2021-02-09T04:33:37+00:00 urn:sha1:ede47ac1476bcc3769a280103ed76d6eeb668b2e (From OE-Core rev: cac7f890f6b223006c1c290e76b9d575b729d87d) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-10T23:48:55+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2021-02-09T15:57:17+00:00 urn:sha1:7f4d05758593f3947ecff7df45f56b335e3964e9 (From OE-Core rev: 8ddfab7b185dbba171afce80260e5638eb06a769) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-08T14:47:16+00:00 Khem Raj raj.khem@gmail.com 2021-02-06T06:31:38+00:00 urn:sha1:525493e3efc9480a671dd0cd848923725961fc12 compiler can only use fortify options when some level of optimization is on, otherwise it ends up sending some warnings. warning: _FORTIFY_SOURCE requires compiling with optimization (-O) [-W#warnings] this is usually OK, since -O<level> would be added via CFLAGS to compiler cmdline in normal compile stages, however during configure there are problems when CC,CPP,CXX are probed alone in configure tests which results in above warning, which confuses the configure results and autotools 2.70+ detects it as error e.g. configure:17292: error: C preprocessor "riscv32-yoe-linux-clang -target riscv32-yoe-linux -mlittle-endian -mno-relax -Qunused-arguments -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/mnt/b/yoe/master/build/tmp/work/riscv32-yoe-linux/ndpi/3.4-r0/recipe-sysroot -E" fails sanity check See `config.log' for more details therefore adding a -O ( which actually is -O1 ) to lcl_maybe_fortify means we can properly test these configure tests and real -O<level> will still override -O added here, so overrall behavior improves (From OE-Core rev: b6113dd68caa46d56cf3c8293119f2b9d8b137fd) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-07T22:26:42+00:00 Michael Halstead mhalstead@linuxfoundation.org 2021-02-06T02:27:50+00:00 urn:sha1:88cb39cc3cf55ff39c8913e93f497c3c07e9e862 Support glibc 2.33. (From OE-Core rev: 5c7f963d395aa4a94d78c37883488baac471ea43) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-07T22:26:42+00:00 Michael Halstead mhalstead@linuxfoundation.org 2021-02-06T02:22:27+00:00 urn:sha1:987aa920172f8cf8b4854812f623a8c018746cea Final glibc 2.32 based uninative. (From OE-Core rev: 8b5d932a42ce9e3e801837bea9cf319c455d9ae5) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-05T12:00:54+00:00 Khem Raj raj.khem@gmail.com 2021-02-04T21:41:41+00:00 urn:sha1:7b8df042d0c175388d6230f008b1c83d5c5cd5da Drop backported patches (From OE-Core rev: aa87638cf4f2bef66df92f961c7814f6b482fd3d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-02-03T21:45:49+00:00 Khem Raj raj.khem@gmail.com 2021-01-30T07:19:50+00:00 urn:sha1:b7daba67380d5b2d2bae0154372db770ae05b195 Drop backported patches which are already present in 2.36 release (From OE-Core rev: 897afa95ba340f1124decac5753e1d1e1283b515) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-01-31T10:37:16+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2021-01-30T14:18:32+00:00 urn:sha1:fe70db2c46f968ed14e1b24ebc2f70469f6f0cd8 This looks like it was from before the recipe was split, we'd expect the system qemu mode for running the images so the dependency should be updated. (From OE-Core rev: 3a4fed4ae0e8a0d1bd62ea5fa1ef12925e1f20f5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2021-01-29T21:21:53+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2021-01-27T14:46:43+00:00 urn:sha1:cff7db890cdfab41cc8f74e3dc378660d9b6219e We never recommend setting RDEPENDS or RPROVIDES without a package name against them. The default in bitbake.conf is legacy only, drop it. The python recipe was trying to add to the empty variable in the native case fix that too. (From OE-Core rev: b8bbc1bbe282cce2ea4d0ff293f931f6caf6153b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>