From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>,
Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: zsh/pcre module building
Date: Sat, 23 Mar 2002 19:57:11 +0000 [thread overview]
Message-ID: <1020323195712.ZM29012@candle.brasslantern.com> (raw)
In-Reply-To: <1016807054.3021.12.camel@localhost.localdomain>
On Mar 22, 5:24pm, Borsenkow Andrej wrote:
} Subject: Re: PATCH: zsh/pcre module building
}
} > So if I comprehend what's going on here correctly, this links the zsh/pcre
} > module against libpcre, but doesn't link the zsh binary against it?
}
} I have been thinking about it before, just some comments
}
} - I hoped to create implementation that would share configure cache and
} make is possible to list help from every module's configure script using
} top-level configure --help and pass parameters to every module's
} configure script using top-level configure.
That sounds nice, too.
} - linking shared object with dynamic library is not portable. May be it
} works on every modern system nowadays, I do not know.
I believe Clint suggested that we do a configure-time test for whether
this works, and if not then include the shared object's dependencies in
the top-level link. But his patch doesn't do that, yet, I think.
--
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:[~2002-03-23 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 18:07 Clint Adams
2002-03-19 1:29 ` Bart Schaefer
2002-03-22 14:24 ` Borsenkow Andrej
2002-03-23 19:57 ` Bart Schaefer [this message]
2002-03-23 23:47 ` Clint Adams
2002-07-04 17:07 ` Clint Adams
2002-07-05 10:39 ` Borsenkow Andrej
2002-03-21 19:14 ` Borsenkow Andrej
2002-03-21 20:15 ` Peter Stephenson
2002-03-21 20:37 ` Bart Schaefer
2003-06-23 4:35 Fr�d�ric L. W. Meunier
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=1020323195712.ZM29012@candle.brasslantern.com \
--to=schaefer@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).