Re: OK to inject BUILDLINK_PASSTHRU_RPATHDIRS into lang/rust?

["Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>]

Thanks for chiming in as the expert!

While we are on tangents … right now my rust setup doesn't really work
yet. My proposed patch makes rustc work, but I still get failures from
rust land. Now even just when building good old gnuplot, since it now
is affected by rust via libimagequant and libgd, apparently.

  thread 'main' panicked at /tmp/work/pkgsrc/2025Q1-devel/bw/devel/cargo-c/work/vendor/openssl-sys-0.9.102/build/main.rs:417:13:
  OpenSSL libdir at `["/usr/lib64", "/usr/lib"]` does not contain the required files to either statically or dynamically link OpenSSL
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
*** Error code 101

Stop.
bmake[4]: stopped making "install" in /tmp/work/pkgsrc/2025Q1-devel/pkgsrc-41da1554ace8/devel/cargo-c
*** Error code 1

But actually, this seems unrelated to my changes and should trigger on
any modern Linux system? The OpenSSL libraries are (of course! ;-) in

	/usr/lib/x86_64-linux-gnu/libssl.so

and not in /usr/lib64 or /usr/lib/. You mentioned patching
vendor/openssl-src … but I don't see a patch in 2025Q1. I guess one is
needed for me to build cargo-c?

But closer to the contact point of the tangent …

Am Sat, 12 Apr 2025 20:06:15 +0200
schrieb Havard Eidnes <he%NetBSD.org@localhost>:

> Well.  The patches we carry around in the rust package come in a
> few different categories:

What category is

	patch-compiler_rustc__codegen__ssa_src_back_linker.rs

? Are those only things relevant on Darwin, like

-                let mut rpath = OsString::from("@rpath/");
+                let mut rpath = OsString::from("@PREFIX@/lib/");

and the case of locating libunwind specifically? I am confused that
there is a special path needed for one library. Shouldn't all libs in
the search path be found, which should include @PREFIX@/lib?

Just generally: Can you confirm that just moving my bits from
src/bootstrap/builder.rs earlier to src/bootstrap/src/core/builder.rs
is all that's needed to make rust use the same library paths as the
other builds, including BUILDLINK_PASSTHRU_RPATHDIRS? Are possibly
other places that rule in the matter when later building crates?

Even if it won't get merged, I'd like to keep a correct patch that
works and am only wildly guessing for anything rust.


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg