From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yash.Shinde@windriver.com,
openembedded-core@lists.openembedded.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Randy.MacLeod@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0
Date: Tue, 27 Aug 2024 21:41:27 +0100 [thread overview]
Message-ID: <bcf7e4329803a86e3f9cf8ddf3b62564ee5e8532.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-ozQ+3JPRCJyigf2LFJnAzsWNWK7dtfORzZH_Jz+bLuw@mail.gmail.com>
On Tue, 2024-08-27 at 22:38 +0200, Alexander Kanavin wrote:
> On Tue, 27 Aug 2024 at 21:51, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>
> > Shouldn't rust complain if it doesn't work with old compilers? Are
> > the
> > compiler requirements for rust documented anywhere? I'm reluctant
> > to
> > throw buildtools at anything that breaks. In theory we also would
> > need
> > to change the sanity.bbclass compiler versions tests and so on too
> > :/
>
> The specific error seems to be about libz-sys, which carries a copy
> of
> zlib and that is built using host gcc - I suspect that somehow alma9
> gcc is used incorrectly there. This could be a problem on our side,
> I'd need to first try building cargo 1.79.0 directly on alma9 and see
> if that breaks too in the same way, or not. Don't have any more time
> to look into it today.
The failure is building cargo-native iirc so using the host gcc would
be expected there?
Cheers,
Richard
next prev parent reply other threads:[~2024-08-27 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 17:05 [PATCH 1/2] rust: Oe-selftest changes for rust v1.79 Yash.Shinde
2024-08-25 17:05 ` [PATCH 2/2] rust: Upgrade 1.78.0->1.79.0 Yash.Shinde
2024-08-27 10:38 ` [OE-core] " Richard Purdie
2024-08-27 12:11 ` Yash Shinde
2024-08-27 12:24 ` Alexander Kanavin
2024-08-27 12:40 ` Richard Purdie
2024-08-27 12:47 ` Yash Shinde
2024-08-27 13:22 ` Richard Purdie
2024-08-27 16:23 ` Alexander Kanavin
[not found] ` <17EFA275ACF95534.20373@lists.openembedded.org>
2024-08-27 16:25 ` Alexander Kanavin
[not found] ` <17EFA28FD32C2C48.20373@lists.openembedded.org>
2024-08-27 17:16 ` Alexander Kanavin
2024-08-27 19:51 ` Richard Purdie
2024-08-27 20:38 ` Alexander Kanavin
2024-08-27 20:41 ` Richard Purdie [this message]
2024-08-27 20:47 ` Alexander Kanavin
2024-08-27 21:02 ` Khem Raj
2024-08-28 13:11 ` Alexander Kanavin
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=bcf7e4329803a86e3f9cf8ddf3b62564ee5e8532.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.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