Am Thu, 17 Apr 2025 09:11:42 +0200
schrieb "Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>:
> Where should I hack things so that it uses the correct directory? Would
> it be too easy if things would just use pkg-config?
>
> $ pkg-config --variable libdir openssl
> /usr/lib/x86_64-linux-gnu
>
Well … seems like this helps:
diff -ruN pkgsrc-2025Q1/devel/cargo-c/Makefile pkgsrc/devel/cargo-c/Makefile
--- pkgsrc-2025Q1/devel/cargo-c/Makefile 2025-04-02 05:01:42.000000000 +0200
+++ pkgsrc/devel/cargo-c/Makefile 2025-04-17 09:21:29.962754246 +0200
@@ -17,8 +17,8 @@
USE_TOOLS+= pkg-config
RUST_REQ= 1.76.0
-MAKE_ENV+= OPENSSL_DIR=${BUILDLINK_PREFIX.openssl:Q}
-RUSTFLAGS+= -C link-arg=${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.openssl}/lib
+#MAKE_ENV+= OPENSSL_DIR=${BUILDLINK_PREFIX.openssl:Q}
+#RUSTFLAGS+= -C link-arg=${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.openssl}/lib
.include "cargo-depends.mk"
[…]
=> Checking for work-directory references in cargo-c-0.9.32nb1
=> Creating binary package /nfs/ssd2.2/u/sw/work/a770de/pkgsrc/2025Q1-devel/bw/devel/cargo-c/work/.packages/cargo-c-0.9.32nb1.tgz
===> Building binary package for cargo-c-0.9.32nb1
=> Creating binary package /nfs/ssd2.2/u/sw/work/a770de/pkgsrc/2025Q1-devel/pkgsrc-41da1554ace8/packages/All/cargo-c-0.9.32nb1.tgz
===> Installing binary package of cargo-c-0.9.32nb1
So should be drop that part if openssl is built-in?
Regards,
Thomas
--
Dr. Thomas Orgis
Universität Hamburg
Regionales Rechenzentrum / Regional Computing Center
Basis-Infrastruktur / Basic Infrastructure
High-Performance Computing
Schlüterstr. 70
20146 Hamburg
Tel.: +49 40 42838 8826
E-Mail: thomas.orgis%uni-hamburg.de@localhost
Team: hpc%uni-hamburg.de@localhost
https://www.uni-hamburg.de
https://www.rrz.uni-hamburg.de
Attachment:
smime.p7s
Description: S/MIME cryptographic signature