Re: [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0

[Deepesh Varatharajan <deepesh.varatharajan@windriver.com>]

On 12-03-2025 15:22, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 5 Mar 2025 at 14:45, Varatharajan, Deepesh via
> lists.openembedded.org
> <deepesh.varatharajan=windriver.com@lists.openembedded.org> wrote:
>> +++ b/meta/recipes-devtools/rust/files/revert-Zdual-proc-macros-additional-check.patch
>> @@ -0,0 +1,43 @@
>> +rust: Fix build failure for v1.83 when lib32 enabled
>> +
>> +Because of the following commit ,
>> +https://github.com/rust-lang/rust/commit/68034f837a39387e49fc7d7c5b088f5372a1127e
>> +when we enable lib32, getting build failure because there is a check for target
>> +support for "-Zdual-proc-macros" flag not functioning properly when lib32 is
>> +enabled in the build environment. So for now reverting this commit and bring
>> +back the previous behavior, where the "-Zdual-proc-macros" flag is always
>> +added for building proc macros, regardless of the target architecture's support.
>> +This would bypass the check introduced in the patch, allowing the build to
>> +proceed without error, even when building for a 64-bit architecture with lib32 enabled.
>> +
>> +Upstream-Status: Pending
>> +
>> +Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>> +diff --git a/src/bootstrap/src/core/builder.rs b/src/bootstrap/src/core/builder.rs
> Please do not add new 'Pending' patches, especially without specifying
> the reason for not submitting them. They tend to stay 'Pending'
> forever and are discouraged for that reason.
>
> Rather, submit them upstream before sending them to oe-core, mark them
> as Inappropriate (with reason and link to upstream ticket), or in rare
> cases, explain what event needs to happen before 'Pending' status
> becomes something else.
Since the new commit added in 1.83 is causing a failure when multilib is 
enabled, and it is a blocking issue for version 1.83,
the commit has been reverted, and the update has been proceeded with. An 
issue will be raised upstream,
and the patch status will be updated when submitting the 1.84 update.

Regards,
Deepesh

>
> Alex