From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.dk>
Subject: Re: PATCH: "make check" with libzsh (e.g. FreeBSD)
Date: Sun, 3 Jun 2001 18:04:33 +0000 [thread overview]
Message-ID: <1010603180433.ZM24939@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0106031239260.19014-100000@itsrm2.mow.siemens.ru>
On Jun 3, 12:40pm, Andrej Borsenkow wrote:
} Subject: Re: PATCH: "make check" with libzsh (e.g. FreeBSD)
}
} On Sun, 3 Jun 2001, Bart Schaefer wrote:
}
} > This is hardly ever going to be a problem except for someone who is
} > trying to keep up with individual patches.
}
} And these are exactly those who need tests :-)
Actually, I was thinking that the tests are really needed by people who
are building on a new platform for the first time. The developers are
more likely to know what they're doing -- for example, as of right now,
you can't run "make check" for a static build without knowing that you
have to change the default linkage of zpty.
In any case, *re*compiling with a different LD_RUN_PATH doesn't seem to
be an option. We could, however, compile two different zsh binaries --
e.g., zsh and zsh-test -- and use the zsh-test binary for "make check".
On systems without libzsh, zsh-test could just be a link to zsh, but
where libzsh was needed, it'd be a separate binary with LD_RUN_PATH set
to the build directory.
Then we'd have to update the tests to always run zsh-test rather than
just zsh. We'd still need an LD_LIBRARY_PATH patch in Test/Makefile.in
for systems that don't use an LD_RUN_PATH.
--
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
prev parent reply other threads:[~2001-06-03 18:05 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
2001-06-03 8:40 ` Andrej Borsenkow
2001-06-03 18:04 ` Bart Schaefer [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=1010603180433.ZM24939@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).