From: "Khem Raj" <raj.khem@gmail.com>
To: akuster808 <akuster808@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Anton Antonov <Anton.Antonov@arm.com>
Subject: Re: [yocto] meta-parsec build failure
Date: Mon, 5 Jul 2021 17:01:48 -0700 [thread overview]
Message-ID: <CAMKF1sqNSERLVA7VPt+=GEQMucBmFqZofdNbyjXbj1W-x_73AQ@mail.gmail.com> (raw)
In-Reply-To: <8bfb3511-b2b6-1ad1-7271-b72c00cecf3c@gmail.com>
On Mon, Jul 5, 2021 at 4:50 PM akuster808 <akuster808@gmail.com> wrote:
>
>
>
> On 7/5/21 4:15 PM, Khem Raj wrote:
> > yeah perhaps try using -DMBEDTLS_FATAL_WARNINGS=OFF
> I would love to try that out, Where would I apply that?
> mbedtls is a dependent create to a dependent create to parsec-service
> recipe. The Rust paradigm in OE does make my head hurt.
yeah perhaps you need to fork this repo and let main package know via
editing the toml file perhaps.
>
> -armin
> >
> > On Mon, Jul 5, 2021 at 1:57 PM Armin Kuster <akuster808@gmail.com> wrote:
> >> The parsec-service in meta-parsec has been failing ever since gcc 11 was
> >> merged into core.
> >>
> >> https://errors.yoctoproject.org/Errors/Build/123537/
> >>
> >> I have already opened an issue with upstream:
> >> https://github.com/parallaxsecond/rust-psa-crypto/issues/85
> >>
> >> If anyone is interested in this package, I could use an extra set of
> >> eye's on progress of this build failure.
> >>
> >> regards,
> >> Armin
> >>
> >>
> >>
>
prev parent reply other threads:[~2021-07-06 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 20:54 meta-parsec build failure Armin Kuster
2021-07-05 23:15 ` [yocto] " Khem Raj
2021-07-05 23:50 ` Armin Kuster
2021-07-06 0:01 ` Khem Raj [this message]
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='CAMKF1sqNSERLVA7VPt+=GEQMucBmFqZofdNbyjXbj1W-x_73AQ@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=Anton.Antonov@arm.com \
--cc=akuster808@gmail.com \
--cc=yocto@yoctoproject.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 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.