From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
<zsh-workers@sunsite.dk>
Subject: Re: PATCH: "make check" with libzsh (e.g. FreeBSD)
Date: Sun, 3 Jun 2001 00:52:38 +0000 [thread overview]
Message-ID: <1010603005238.ZM11760@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0106022143160.27900-100000@itsrm2.mow.siemens.ru>
On Jun 2, 9:48pm, Andrej Borsenkow wrote:
} Subject: Re: PATCH: "make check" with libzsh (e.g. FreeBSD)
}
} The actual problem is interaction between LD_RUN_PATH encoded in
} executable and LD_LIBRARY_PATH. I.e. when two libraries exist, which
} one is used. It may result in obscure test failures.
This is hardly ever going to be a problem except for someone who is
trying to keep up with individual patches. For everyone else, the
version number will change between installs.
} The only proper workaround is to recompile zsh with different LD_RUN_PATH
} value. Or use libtool - I guess, it is quite usable now.
I've had nothing but trouble with it the last several times I tried to
use it. Not because of any particular flaw in its function, but because
it now depends on the availability of various compatibility libraries,
which I've been unable to compile because they in turn depend on the very
latest gcc/glibc, or for various other reasons.
IMO using libtool would have the opposite of the intended effect -- it
would restrict the number of platforms on which zsh can easily be compiled.
However, I'm prepared to be convinced otherwise.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-03 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 15:49 Bart Schaefer
2001-06-02 17:48 ` Andrej Borsenkow
2001-06-03 0:52 ` Bart Schaefer [this message]
2001-06-03 8:40 ` Andrej Borsenkow
2001-06-03 18:04 ` 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=1010603005238.ZM11760@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.dk \
/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).