native: Use a native site file and ensure the correct sed is used
native recipes were not using the site files. There are some things we need to correct such as not using the path to sed-native. This allows us to deploy settings globally for all recipes rather than hacking around then in individual recipes as libtool-native used to for sed. This fixes a regression introduced by http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=32edeb391f2107bb66b361cdcd4b8d4447731c33 (From OE-Core rev: db2eb3258844458569b7d4e6ed82c345858a3b99) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
db51dd22fa
commit
08d902ac8f
|
@ -54,7 +54,7 @@ DEPENDS_GETTEXT = "gettext-native"
|
|||
PTEST_ENABLED = "0"
|
||||
|
||||
# Don't use site files for native builds
|
||||
export CONFIG_SITE = ""
|
||||
export CONFIG_SITE = "${COREBASE}/meta/site/native"
|
||||
|
||||
# set the compiler as well. It could have been set to something else
|
||||
export CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
|
||||
|
|
|
@ -0,0 +1 @@
|
|||
ac_cv_path_SED=sed
|
Loading…
Reference in New Issue