From: Khem Raj <raj.khem@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] bitbake.conf: drop _build-${BUILD_OS} over-ride
Date: Wed, 9 May 2018 22:44:21 -0700 [thread overview]
Message-ID: <86e5dada-7bd6-5cbb-95ff-0bf9ccdf0e1e@gmail.com> (raw)
In-Reply-To: <1525922097-15292-3-git-send-email-armccurdy@gmail.com>
On 5/9/18 8:14 PM, Andre McCurdy wrote:
> Building on a host OS other than a recent version of Linux is not
> recommended or supported. Drop the historical _build-${BUILD_OS}
> over-ride to avoid giving the impression that other host OS's might
> be supported.
if this is not causing issues, I would suggest to keep this in.
>
> Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
> ---
> meta/classes/cross.bbclass | 1 -
> meta/classes/native.bbclass | 1 -
> meta/conf/bitbake.conf | 2 +-
> 3 files changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/meta/classes/cross.bbclass b/meta/classes/cross.bbclass
> index 4e85cab2..34d7951 100644
> --- a/meta/classes/cross.bbclass
> +++ b/meta/classes/cross.bbclass
> @@ -37,7 +37,6 @@ CPPFLAGS = "${BUILD_CPPFLAGS}"
> CFLAGS = "${BUILD_CFLAGS}"
> CXXFLAGS = "${BUILD_CFLAGS}"
> LDFLAGS = "${BUILD_LDFLAGS}"
> -LDFLAGS_build-darwin = "-L${STAGING_LIBDIR_NATIVE}"
>
> TOOLCHAIN_OPTIONS = ""
>
> diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
> index ad7e98a..ddccfe2e1 100644
> --- a/meta/classes/native.bbclass
> +++ b/meta/classes/native.bbclass
> @@ -44,7 +44,6 @@ CPPFLAGS = "${BUILD_CPPFLAGS}"
> CFLAGS = "${BUILD_CFLAGS}"
> CXXFLAGS = "${BUILD_CXXFLAGS}"
> LDFLAGS = "${BUILD_LDFLAGS}"
> -LDFLAGS_build-darwin = "-L${STAGING_LIBDIR_NATIVE} "
>
> STAGING_BINDIR = "${STAGING_BINDIR_NATIVE}"
> STAGING_BINDIR_CROSS = "${STAGING_BINDIR_NATIVE}"
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index a772cab..702f498 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -735,7 +735,7 @@ DISTRO_NAME ??= "OpenEmbedded"
> #
> # This works for functions as well, they are really just environment variables.
> # Default OVERRIDES to make compilation fail fast in case of build system misconfiguration.
> -OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable"
> +OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable"
> LIBCOVERRIDE ?= ""
> CLASSOVERRIDE ?= "class-target"
> DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"
>
next prev parent reply other threads:[~2018-05-10 5:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 3:14 [PATCH 1/3] bitbake.conf: make libc over-ride lower priority than _forcevariable Andre McCurdy
2018-05-10 3:14 ` [PATCH 2/3] native.bbclass: drop _virtclass-native and _virtclass-nativesdk overrides Andre McCurdy
2018-05-10 3:14 ` [PATCH 3/3] bitbake.conf: drop _build-${BUILD_OS} over-ride Andre McCurdy
2018-05-10 5:44 ` Khem Raj [this message]
2018-05-10 15:47 ` Dan McGregor
2018-05-10 16:33 ` Burton, Ross
2018-05-10 17:09 ` Dan McGregor
2018-05-10 17:57 ` Christopher Larson
2018-05-10 5:41 ` [PATCH 1/3] bitbake.conf: make libc over-ride lower priority than _forcevariable Khem Raj
2018-05-10 22:33 ` Andre McCurdy
2018-05-10 22:40 ` Khem Raj
2018-05-11 0:53 ` Andre McCurdy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86e5dada-7bd6-5cbb-95ff-0bf9ccdf0e1e@gmail.com \
--to=raj.khem@gmail.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox