All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yash Shinde <Yash.Shinde@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: "MacLeod, Randy" <randy.macleod@windriver.com>,
	"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: [RFC] rust: Upgrade 1.85.1->1.86.0
Date: Fri, 23 May 2025 21:52:09 +0530	[thread overview]
Message-ID: <83e0d268-ec47-4f3a-bf05-2aee4e58e749@windriver.com> (raw)

Hello everyone,

I am working on upgrading rust to v1.86.0 and this time there were a 
bunch of
dependencies to be included and some errors as well.

A complete breakdown of the changes for this version upgrade is available
in the commit message of a branch pushed in poky-contrib.
https://git.yoctoproject.org/poky-contrib/log/?h=harish/rust_v1.86.0
(I haven't tested with Ross's patches that remove python3-native and 
file-native DEPENDS yet.)


do_package_qa: QA Issue: File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/bin/rust-lld
in package rust doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]

One of the issues I encountered was the QA error mentioned above and 
here's my analysis:
I attempted to address some package QA errors related to LDFLAGS by 
using TARGET_CC_ARCH += "${LDFLAGS}",
(Like done here: 
https://git.yoctoproject.org/poky/commit/?id=cc24a0ff76f2e227cc3a0f478d078b2158299a80
https://git.yoctoproject.org/poky/log/?qt=grep&q=GNU_HASH)
but unfortunately, this approach didn’t resolve the issue.(Is there any 
specific task/way to add it?)

Although including ldflags in INSANE_SKIP isn’t ideal, but that proved 
effective after trying other alternatives.

Please review the proposed upgrade changes.
I would appreciate any feedback or suggestions.


Regards,
Yash.



             reply	other threads:[~2025-05-23 16:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 16:22 Yash Shinde [this message]
2025-05-27 12:47 ` [OE-core] [RFC] rust: Upgrade 1.85.1->1.86.0 Alexander Kanavin
     [not found] ` <184363192F51E64D.13855@lists.openembedded.org>
2025-05-27 13:40   ` Alexander Kanavin
2025-05-27 14:40     ` Yash Shinde
2025-05-27 14:06 ` Alexander Kanavin
2025-05-27 14:42   ` Yash Shinde
2025-05-27 16:26     ` Alexander Kanavin
2025-05-30  2:32       ` Khem Raj
2025-05-30 12:42         ` Yash Shinde
2025-05-30 13:15           ` Alexander Kanavin
2025-06-02 11:15             ` Yash Shinde
2025-06-02 13:03               ` Randy MacLeod
2025-06-02 17:09                 ` Khem Raj
2025-06-03 18:31                   ` Randy MacLeod
2025-06-03 20:56                     ` Khem Raj
2025-06-06 12:50                     ` Yash Shinde
2025-06-06 12:57                       ` Yash Shinde
2025-06-03 19:14               ` Randy MacLeod

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=83e0d268-ec47-4f3a-bf05-2aee4e58e749@windriver.com \
    --to=yash.shinde@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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.