From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago][master/kirkstone][PATCH] clacc: Fix TARGET name
Date: Fri, 2 Jun 2023 15:11:23 -0400 [thread overview]
Message-ID: <20230602191123.GP9226@denix.org> (raw)
In-Reply-To: <20230602182716.2344-1-reatmon@ti.com>
On Fri, Jun 02, 2023 at 01:27:16PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> The last update that fixed the syntax of changing _ to : was a little
> too aggressive and changed the TARGET values incorrectly.
Might want to drop this comment:
> Not sure why it took this long to see this pop up.
Because opencl was disabled since dunfell until this commit:
https://git.yoctoproject.org/meta-arago/commit/?id=1e2df30581aeb8c6f0e60bc0be788bc36f0f9d6a
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> meta-arago-extras/recipes-ti/openmpacc/clacc_git.bb | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta-arago-extras/recipes-ti/openmpacc/clacc_git.bb b/meta-arago-extras/recipes-ti/openmpacc/clacc_git.bb
> index 4d78e7b7..f56d65cc 100644
> --- a/meta-arago-extras/recipes-ti/openmpacc/clacc_git.bb
> +++ b/meta-arago-extras/recipes-ti/openmpacc/clacc_git.bb
> @@ -9,9 +9,9 @@ RDEPENDS:${PN} += "clocl"
>
> S = "${WORKDIR}/git/host"
>
> -TARGET:class-target = "clacc:arm"
> -TARGET:class-native = "clacc:x86"
> -TARGET:class-nativesdk = "clacc:x86"
> +TARGET:class-target = "clacc_arm"
> +TARGET:class-native = "clacc_x86"
> +TARGET:class-nativesdk = "clacc_x86"
>
> export LINUX_DEVKIT_ROOT = "${STAGING_DIR_HOST}"
> export X86_HOST_ROOT = "${STAGING_DIR_HOST}"
> --
> 2.17.1
next prev parent reply other threads:[~2023-06-02 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:27 [meta-arago][master/kirkstone][PATCH] clacc: Fix TARGET name Ryan Eatmon
2023-06-02 19:11 ` Denys Dmytriyenko [this message]
2023-06-02 20:06 ` Ryan Eatmon
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=20230602191123.GP9226@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.