From: Jos Backus <josb@cncdsl.com>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh and autoconf-2.50
Date: Wed, 30 May 2001 23:22:09 -0700 [thread overview]
Message-ID: <20010530232209.B49870@lizzy.bugworks.com> (raw)
In-Reply-To: <1010531045212.ZM5393@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Thu, May 31, 2001 at 04:51:50AM +0000
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Thu, May 31, 2001 at 04:51:50AM +0000, Bart Schaefer wrote:
> You really can't use purify very well on a program that does its own
> dynamic loading. You will need --disable-dynamic.
That's what I thought; thanks for confirming this.
> Have you tried reading the INSTALL file?
I have now, sorry :-/
> There's a large section titled "Adding and removing modules". The short
> answer is that you edit the config.modules file and change the values of
> `link' and `auto' on the line for the zpty module to be `static' and `no'
> respectively.
Got it, thanks.
I have attached the Purify results of a ``gmake check'', hopefully that's OK
(it's not that big). Please let me know if there is anything else I can do.
--
Jos Backus _/ _/_/_/ "Modularity is not a hack."
_/ _/ _/ -- D. J. Bernstein
_/ _/_/_/
_/ _/ _/ _/
josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer;
[-- Attachment #2: zsh-purify.tar.gz --]
[-- Type: application/x-tar-gz, Size: 8108 bytes --]
next prev parent reply other threads:[~2001-05-31 6:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 22:53 Jos Backus
2001-05-30 23:23 ` Wayne Davison
2001-05-30 23:50 ` Jos Backus
2001-05-31 0:12 ` Bart Schaefer
2001-05-31 1:15 ` Jos Backus
2001-05-31 4:52 ` Bart Schaefer
2001-05-31 6:22 ` Jos Backus [this message]
2001-05-31 7:22 ` Bart Schaefer
2001-05-31 9:34 ` Sven Wischnowsky
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 23:15 Jos Backus
2001-05-30 21:48 Jos Backus
2001-05-30 22:02 ` Bart Schaefer
2001-05-30 22:28 ` Jos Backus
2001-05-30 22:40 ` Clint Adams
2001-05-31 0:08 ` Bart Schaefer
2001-05-31 13:40 ` Clint Adams
2001-05-31 13:53 ` Oliver Kiddle
2001-05-31 14:24 ` Clint Adams
2001-05-31 17:34 ` Akim Demaille
2001-05-31 17:51 ` Clint Adams
2001-05-31 18:01 ` Akim Demaille
2001-06-01 8:55 ` Andrej Borsenkow
2001-06-01 11:00 ` Akim Demaille
2001-06-01 16:48 ` Tim Van Holder
2001-06-01 9:37 ` Peter Stephenson
2001-06-01 12:27 ` Clint Adams
2001-06-01 12:45 ` Peter Stephenson
2001-06-01 12:54 ` Andrej Borsenkow
2001-06-01 13:33 ` Peter Stephenson
2001-06-01 13:47 ` Bart Schaefer
2001-06-01 13:56 ` Peter Stephenson
2001-06-01 13:57 ` Andrej Borsenkow
2001-06-01 14:05 ` Andrej Borsenkow
2001-06-01 14:08 ` Clint Adams
2001-06-01 14:19 ` Andrej Borsenkow
2001-06-01 14:25 ` Peter Stephenson
2001-06-01 14:36 ` Andrej Borsenkow
2001-06-01 15:05 ` Clint Adams
2001-06-01 14:19 ` Peter Stephenson
2001-06-01 14:11 ` Peter Stephenson
2001-05-30 22:34 ` Clint Adams
2001-05-30 22:44 ` Jos Backus
2001-05-31 8:25 ` Andrej Borsenkow
2001-05-31 13:44 ` Clint Adams
2001-05-31 13:59 ` Andrej Borsenkow
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=20010530232209.B49870@lizzy.bugworks.com \
--to=josb@cncdsl.com \
--cc=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).