From: Marijn <hkBst@gentoo.org>
To: Matthew Flatt <mflatt@cs.utah.edu>
Cc: "dev@racket-lang.org" <dev@racket-lang.org>,
Bigloo Mailing list <bigloo@sophia.inria.fr>,
gentoo-lisp@lists.gentoo.org
Subject: [gentoo-lisp] Re: [racket-dev] racket unlinking bigloo lib
Date: Thu, 12 Jan 2012 10:25:48 +0100 [thread overview]
Message-ID: <4F0EA71C.7050505@gentoo.org> (raw)
In-Reply-To: <20120110142512.505436500A1@mail-svr1.cs.utah.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10-01-12 15:25, Matthew Flatt wrote:
> At Tue, 10 Jan 2012 11:31:19 +0100, Marijn wrote:
>> Racket calls `ldconfig -n /usr/lib' in the course of doing `make
>> install' and this causes one of bigloo's shared object symlinks
>> to be unlinked. I don't think racket should be calling ldconfig.
>
> That call comes from `libtool --mode=finish'. I'm no libtool
> expert,but my understanding is that `libtool --mode=finish' is
> needed in general when installing via `libtool'.
I'm far from an expert on libtool.
Using DESTDIR everything including shared libraries is installed in a
staging area by `make install'. Files will only be moved to the ``live
filesystem'' by the package manager after things like make install
have finished running. Currently `libtool --mode=finish' is run on the
``live filesystem'' library directory. This should not have any effect
on anything in the staging area.
Thus `libtool --mode=finish' should either be run on the DESTDIR
staging area or not at all.
Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8OpxwACgkQp/VmCx0OL2z5BwCffdwgsr8LNua1whRL+WRawQ6a
VasAoIqZPcXdzllC4X8WchOlK/rxmeGa
=f3vP
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-01-12 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 10:31 [gentoo-lisp] racket unlinking bigloo lib Marijn
[not found] ` <20120110142512.505436500A1@mail-svr1.cs.utah.edu>
2012-01-12 9:25 ` Marijn [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=4F0EA71C.7050505@gentoo.org \
--to=hkbst@gentoo.org \
--cc=bigloo@sophia.inria.fr \
--cc=dev@racket-lang.org \
--cc=gentoo-lisp@lists.gentoo.org \
--cc=mflatt@cs.utah.edu \
/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