From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: Zsh hacking and development <zsh-workers@math.gatech.edu>
Subject: Re: zsh-3.1.0-test3 release
Date: Mon, 18 Nov 1996 14:41:34 +0300 (MOW) [thread overview]
Message-ID: <Pine.SV4.3.95.961118143422.35A-100000@itsrm1.mow.sni.de> (raw)
In-Reply-To: <199611170427.FAA13416@hzoli.ppp.cs.elte.hu>
On Sun, 17 Nov 1996, Zoltan Hidvegi wrote:
>
> It may now support dynamic loading on SVR4 systems. Try it. If it does not
> work, send a patch to fix it.
>
Yes, it works. There is a small problem in linking libzsh.so - I have to
think it over. In short:
zsh is linked with -ltermcap. But now termcap functions are used in
libzsh.so and not in zsh. If termcap is static (and we have only static
version), it is not used when linking, and I get run-time error when
accessing termcap functions.
Probably, we need to split LIBS between those neede for zsh itself (does
it need any at all?) and libzsh.so. As the whole code is now in libzsh.so,
probably it is enough:
zsh: $(PROTO) $(ANSI@U@KNR) $(@L@IBZSH) $(@L@OBJS)
$(LINK) $(@L@OBJS) -lzsh
$(LIBZSH): $(LIBOBJS)
$(DLLD) $(LDFLAGS) $(DLLDFLAGS) -o $(LIBZSH) $(LIBOBJS) $(LIBS)
ln -sf $(LIBZSH) libzsh.so
where libs doesn't include -lzsh?
BTW it would be nice to be able to compile static as well as dynamic
version of zsh from te same Makefile.
Thanks!
-------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 252 01 05
SNI ITS Moscow Tel: +7 (095) 252 13 88
NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------
next prev parent reply other threads:[~1996-11-18 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-17 4:27 Zoltan Hidvegi
1996-11-17 7:29 ` Geoff Wing
1996-11-17 7:40 ` Geoff Wing
1996-11-17 16:44 ` Zoltan Hidvegi
1996-11-18 11:41 ` Andrej Borsenkow [this message]
1996-11-20 1:32 ` Zoltan Hidvegi
1996-11-19 10:24 ` Bart Schaefer
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=Pine.SV4.3.95.961118143422.35A-100000@itsrm1.mow.sni.de \
--to=borsenkow.msk@sni.de \
--cc=hzoli@cs.elte.hu \
--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).