Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.6 2018-09-11T08:05:35+00:00 2018-09-11T08:05:35+00:00 Nathan Rossi nathan@nathanrossi.com 2018-09-10T12:45:03+00:00 urn:sha1:09bc7331a44d6e2bbcf0fb693fcb642a6ce61b71 Without a libc the gcc-runtime provider of compilerlibs does not compile. As such avoid the default dependence on the virtual/${TARGET_PREFIX}compilerlibs provider. (From OE-Core rev: 61eead0cdd1f44d8c850f8e4c7389ef444bcd591) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-09-11T08:05:35+00:00 Nathan Rossi nathan@nathanrossi.com 2018-09-10T12:44:13+00:00 urn:sha1:a71dbdee2ffbe2ef87d7b0f22c5fefeda668c6f0 With GCCPIE being enabled by default with security_flags.inc the compiler will by default attempt to compile and link programs as PIE. The targets that use newlib and baremetal in general do not support PIE or are otherwise unable to use it due to how embedded targets are compiled and executed. As such it makes sense to disable PIE by default for these libc's in order to prevent build failures. For baremetal tclibc there are no libc features or implementation as such there is no implementation for the strong stack protector by default. (From OE-Core rev: dfe434b793c156a87b5ead5cb85fe60d920d69d3) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-05-22T12:13:33+00:00 Andre McCurdy armccurdy@gmail.com 2018-05-10T03:14:55+00:00 urn:sha1:2811907b1aefa50cb44c1509996ca8e80c6a84f4 Fix long standing quirk, _forcevariable is documented as being the highest priority over-ride. (From OE-Core rev: b3598b8f1ed1cdc7849e1e4f30d618e87e1bf582) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-05-08T15:14:14+00:00 Alejandro Enedino Hernandez Samaniego alejandro.enedino.hernandez-samaniego@xilinx.com 2018-05-07T21:50:14+00:00 urn:sha1:27dca7d2e955370166042c05aef1524fe1fbc70b When trying to build meta-toolchain using TCLIBC = "baremetal" bitbake throws an error due to a mising dependency: ERROR: Nothing PROVIDES 'virtual/crypt' glibc PROVIDES virtual/crypt but was skipped: PREFERRED_PROVIDER_virtual/libc set to musl, not glibc musl PROVIDES virtual/crypt but was skipped: PREFERRED_PROVIDER_virtual/i586-poky-elf-libc-for-gcc set to baremetal, not musl libxcrypt PROVIDES virtual/crypt but was skipped: Recipe only applies in nativesdk case for now This is caused by the changes on commit: 29f65bda6d2c9fea4adb125c4857ee64f9312b9f nativesdk-glibc: Split glibc and libcrypt to use libxcrypt instead This is where the concept of virtual/crypt was introduced. This patch adds virtual/crypt to ASSUME_PROVIDED on tclibc-baremetal, providing the missing wiring to build meta-toolchain on baremetal correctly. (From OE-Core rev: 26a93d2bf7504bf5f3adb085ed2882ae1b1a3701) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2015-08-30T11:35:50+00:00 Juro Bystricky juro.bystricky@intel.com 2015-08-22T16:55:15+00:00 urn:sha1:2dd0c1d4e1ac1e908cca8586d1dcc3f9a93bbd8d Support for TCLIBC="baremetal". Allows building "baremetal" toolchains. (From OE-Core rev: f1972eea0145ca54f0c087c0f29fd2e54d6b95e8) (From OE-Core rev: cb010e306a6a856c589db5f41fdcaea4e5035d93) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>