Re: pkg/58506: lang/rust-1.79 build fails due to APIs removed in curl-8.8

[Phil Krylov <phil+netbsd%krylov.eu@localhost>]

The following reply was made to PR pkg/58506; it has been noted by GNATS.

From: Phil Krylov <phil+netbsd%krylov.eu@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: tnn%NetBSD.org@localhost
Subject: Re: pkg/58506: lang/rust-1.79 build fails due to APIs removed in
 curl-8.8
Date: Mon, 29 Jul 2024 13:51:36 +0200

 On 2024-07-29 12:40, Tobias Nygren wrote:
 >  I will think about how to do the patch differently of we can
 >  fix this in the curl crate.
 >  Meanwhile you can try to revert this commit and see if anything 
 > changes:
 > 
 >  http://mail-index.netbsd.org/pkgsrc-changes/2024/07/27/msg303751.html
 > 
 >  For reference, prior thread on this topic and why we have the
 >  libunwind patch:
 > 
 >  http://mail-index.netbsd.org/pkgsrc-users/2024/04/03/msg039271.html
 
 Thanks for the context! I believe, trying to revert the libunwind patch 
 will revert to the situation from 
 https://us-central.manta.mnx.io/pkgsrc/public/reports/Linux/el9/trunk/x86_64/20240725.2158/rust-1.79.0/build.log 
 (a Linux build just before the libunwind patch): it fails with `/bin/ld: 
 cannot find -lunwind`.
 
 However, my `BUILDLINK_FILES_CMD.curl=      ${TRUE}` patch seems to fix 
 at least CentOS 7 build. Is anything wrong with it?
 
 Patching the crate version seems hard (I have tried it and AFAICR cargo 
 complains about checksums etc.), probably another option is upgrading to 
 rust-1.80 where the crate is already updated. It needs to be done 
 anyway, but it can take longer, and then Linux is left with broken Rust 
 and 5000 of its dependents for the time being.
 
 -- Ph.