From: Andrew Main <zefram@tao.co.uk>
To: borsenkow.msk@sni.de
Cc: zefram@tao.co.uk, zsh-workers@math.gatech.edu
Subject: Re: PATCH: $(LIBZSH) installation
Date: Fri, 16 Jan 1998 11:32:58 +0000 (GMT) [thread overview]
Message-ID: <199801161132.LAA03259@taos.demon.co.uk> (raw)
In-Reply-To: <Pine.SV4.3.95.980116141251.16351D-100000@itsrm1> from "Andrej Borsenkow" at Jan 16, 98 02:21:07 pm
Andrej Borsenkow wrote:
> Actually, if you just
>link against $(LIBZSH) $(LIBS), zsh will look for *this partucular name*
>(be it libzsh-$VERSION).so or for that matter libzsh.so.$(VERSION)), so
>you can just drop it in the standard place (it won't conflict with old
>version anyway).
Define `standard place'. We already have a zsh-specific lib directory;
it would be nice to keep all zsh's files together, and we can't assume
that any particular directory to which we can write will be searched by
default for libraries.
>Standard way to fo it on SVR4 is to set LD_RUN_PATH:
>
>LD_RUN_PATH=$(libdir)/zsh $(LD) ...
OK, better use that instead of -R. Are there any platforms that need
libzsh but don't accept LD_RUN_PATH? Or should I just assume that there
are, and write another configure test?
>Hmmm ... When building a new (test) version I won't like to overrided my
>(login and so far favorite) shell. I would really prefer to install mods
>and lib (to avoid fiddling with LD_LIBRARY_PATH/module_path) and just
>start new shell from build dir.
Hmmm ... I don't see a problem with temporarily setting
LD_LIBRARY_PATH=$PWD for testing purposes. Still, as there does seem
to be some use in installing the library without the binary, I suppose
we should have a separate target for it. I'd still like install.bin to
install the library, so that "make install.bin" will install a *usable*
binary on all systems.
-zefram
prev parent reply other threads:[~1998-01-16 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-16 10:16 Andrew Main
1998-01-16 11:21 ` Andrej Borsenkow
1998-01-16 11:32 ` Andrew Main [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=199801161132.LAA03259@taos.demon.co.uk \
--to=zefram@tao.co.uk \
--cc=borsenkow.msk@sni.de \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).