From: Khem Raj <raj.khem@gmail.com>
To: Sinan Kaya <okaya@kernel.org>
Cc: Sinan Kaya <sinan.kaya@microsoft.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
Changyi Li <Changyu.Li@microsoft.com>
Subject: Re: [meta-oe][PATCH] abseil-cpp: add recipe for git version
Date: Sun, 9 Feb 2020 10:40:58 -0800 [thread overview]
Message-ID: <CAMKF1spONv-2fZ676CSPjAHbDwzKAABqBHa0Obj2=0+osj84ZQ@mail.gmail.com> (raw)
In-Reply-To: <ebdd6807-4f9b-f1aa-fcdf-dba5ab71715e@kernel.org>
On Sun, Feb 9, 2020 at 9:45 AM Sinan Kaya <okaya@kernel.org> wrote:
>
> On 2/9/2020 11:56 AM, Khem Raj wrote:
> > It also fails to build on musl
> > https://errors.yoctoproject.org/Errors/Details/390527/
> >
> > On Sat, Feb 8, 2020 at 11:53 PM Khem Raj <raj.khem@gmail.com> wrote:
>
>
> This library requires "-march=armv8-a+crypto"
>
> -fvisibility-inlines-hidden
>
> Yet, it is getting compiled with: -march=armv8-a+crc
>
This means the recipe should be checking for crypto being present in
TUNE_FEATURES
and be marked incompatible if this is not available.
mark it compatible only on architectures where
it works which it seems are only arm/x86, and on aarch64 particularly
check for CPU feature it requires
something on the lines below
python () {
arch = d.getVar("TARGET_ARCH")
if arch == "aarch64":
tunes = d.getVar("TUNE_FEATURES")
if not tunes:
return
pkgn = d.getVar("PN")
pkgv = d.getVar("PV")
if "crypto" not in tunes:
raise bb.parse.SkipPackage("%s-%s Needs support for crypto
on armv8" % (pkgn, pkgv))
}
> What's the bet way to handle this
next prev parent reply other threads:[~2020-02-09 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 3:46 [meta-oe][PATCH] abseil-cpp: add recipe for git version Sinan Kaya
2020-02-09 7:53 ` Khem Raj
2020-02-09 16:56 ` Khem Raj
2020-02-09 17:45 ` Sinan Kaya
2020-02-09 18:40 ` Khem Raj [this message]
2020-02-10 16:33 ` Sinan Kaya
2020-02-10 17:14 ` Sinan Kaya
2020-02-10 17:22 ` Andrey Zhizhikin
2020-02-10 17:39 ` Sinan Kaya
2020-02-10 16:31 ` Sinan Kaya
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='CAMKF1spONv-2fZ676CSPjAHbDwzKAABqBHa0Obj2=0+osj84ZQ@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=Changyu.Li@microsoft.com \
--cc=okaya@kernel.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sinan.kaya@microsoft.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.