From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: help-guix@gnu.org
Subject: Re: How do I use wrap-ruby-program to make curl findable in a Ruby package?
Date: Tue, 06 Feb 2024 13:42:43 +0100 [thread overview]
Message-ID: <4857152.LvFx2qVVIh@akashi> (raw)
In-Reply-To: <87fry5iy1n.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
06.02.2024 13:20:52 CET Carlo Zancanaro:
> On Mon, Feb 05 2024, Marek Paśnikowski wrote:
> > After many hours of searching and thinking I found the following code
>
> > works:
> I'm glad you got something working. Using wrap-program like this will
> likely work, but with the downside that LD_LIBRARY_PATH will also be
> inherited by any child processes. This might be fine for ruby-nano-bots,
> but this has caused me serious compatibility problems in the past.
If my logic is correct, this should be mitigated somewhat by placing the
needed library path at the end of the $LD_LIBRARY_PATH ? Which is why I opted
for the ~suffix~ argument in the ~wrap-program~ .
>
> Usually, I prefer to store a reference to the precise library in the
> store, rather than setting LD_LIBRARY_PATH. I'm not really sure how to
> do that in your case, because I'm not familiar with ruby-nano-bots or
> any of its dependencies.
I believe this exact behaviour is achieved by ~(search-input-file inputs "lib/
libcurl.so")~ . When I first attempted to build the ~wrap-program~ call I had
a nesting error which explicitly showed that "/gnu/store/hash-curl/lib" is of
unexpected type. Am I wrong?
Sincerely,
Marek Paśnikowski
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-06 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 9:39 How do I use wrap-ruby-program to make curl findable in a Ruby package? Marek Paśnikowski
2024-02-05 20:35 ` Marek Paśnikowski
2024-02-06 12:20 ` Carlo Zancanaro
2024-02-06 12:42 ` Marek Paśnikowski [this message]
2024-02-06 13:28 ` Carlo Zancanaro
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=4857152.LvFx2qVVIh@akashi \
--to=marek@marekpasnikowski.pl \
--cc=help-guix@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.