unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Thomas Morley <thomasmorley65@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 2.9.4 Released [beta]
Date: Mon, 26 Aug 2019 15:12:47 -0400	[thread overview]
Message-ID: <87sgpnoi45.fsf@netris.org> (raw)
In-Reply-To: <CABsfGyVJrUSgcWL35kioq4G8s5uSEk=Q9R1nyD7+AQbLkNg8vQ@mail.gmail.com> (Thomas Morley's message of "Mon, 26 Aug 2019 20:13:45 +0200")

Hi Thomas,

Thomas Morley <thomasmorley65@gmail.com> writes:

> Am Mo., 26. Aug. 2019 um 19:10 Uhr schrieb <tomas@tuxteam.de>:
>>
>> Perhaps you have to add /usr/local/lib to /etc/ld.so.conf (or some
>> file below /etc/ld.so.conf.d) and run ldconfig.
>>
>> HTH
>> -- tomás
>
> Hi tomás,
>
> thanks for your hints.
> I've got it work by running nothing else than
> sudo ldconfig
>
> But I wonder, shouldn't it work out of the box with 'sudo make install' ?

Running 'ldconfig' is not always appropriate, and therefore the vast
majority of programs do *not* run 'ldconfig' in "make install".  Whether
it is appropriate depends on several factors, including which OS and
distro you're using, which prefix you're installing to, whether you're
building a distro package that will actually be installed at a later
time, and which of several available mechanisms you have chosen to use
to allow programs to find their shared libraries.

For example, it's *never* appropriate to run 'ldconfig' on NixOS or Guix
systems, nor when building a Debian package or similar where the actual
installation will happen later, nor when installing into a directory
that's not listed in /etc/ld.so.conf (or /etc/ld.so.conf.d), nor when
running "make install" as non-root.

In theory we could try to make a guess, but there's no reliable way for
the build system to know whether it is appropriate or not, and in
practice it is usually done as a separate step in most modern systems.

     Regards,
       Mark



  parent reply	other threads:[~2019-08-26 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25 20:21 GNU Guile 2.9.4 Released [beta] Andy Wingo
2019-08-26 16:39 ` Thomas Morley
2019-08-26 17:10   ` tomas
2019-08-26 18:13     ` Thomas Morley
2019-08-26 19:07       ` tomas
2019-08-26 19:12       ` Mark H Weaver [this message]
2019-08-26 19:39         ` tomas
2019-08-26 21:06         ` Thomas Morley
     [not found] <cef65c5c-d0e9-02a2-26a1-3cbbe64ac934@gmail.com>
2019-08-29  0:21 ` Matt Wette

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgpnoi45.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=thomasmorley65@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).