Void Linux discussion
 help / color / mirror / Atom feed
From: Juan RP <xtr...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Libraries in program-packages?
Date: Fri, 16 Jan 2015 12:07:32 -0800 (PST)	[thread overview]
Message-ID: <762da557-f681-4b50-aa04-81af2b4384d2@googlegroups.com> (raw)
In-Reply-To: <21529b03-5a50-4a33-bec5-1764559c7050@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 510 bytes --]

Hi,

- Adding the missing shared libraries to the package into a private 
directory and using LD_LIBRARY_PATH is perfectly fine,
  you can create a wrapper to set up this.

- Another way would be using `patchelf` to add a RPATH to the binary, this 
way you wouldn't need to use LD_LIBRARY_PATH.

To make `xbps-src` ignore the unmet shared libraries you can set 
`allow_unknown_shlibs=1` in the template to ignore them.

Either way you'll have to add the missing shared libraries into the package.

[-- Attachment #1.2: Type: text/html, Size: 550 bytes --]

      reply	other threads:[~2015-01-16 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 20:01 Stefan Mühlinghaus
2015-01-16 20:07 ` Juan RP [this message]

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=762da557-f681-4b50-aa04-81af2b4384d2@googlegroups.com \
    --to="xtr..."@gmail.com \
    --cc=voidlinux@googlegroups.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).