From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Unable to build zsh with pcre on Mac Homebrew
Date: Mon, 7 Jan 2019 20:37:14 +0100 [thread overview]
Message-ID: <CABZhJg9udPdFr4vvHLRTnSft5rLCr3CFGiwweE=5C1oeXjH_fg@mail.gmail.com> (raw)
In-Reply-To: <1546875714.4214.10.camel@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Mon, Jan 7, 2019 at 4:43 PM Peter Stephenson <p.stephenson@samsung.com>
wrote:
> That's for you to decide. You say you've done something (you haven't
> told us what) that you think will make it work. Presumably that means
> you think you've somewhere added in the library information for pcre?
> It's not showing up in the output shown below, which suggests it's not
> in the LIBS shell variable in configure at that point.
>
Sorry for the badly specified questions, Peter: it was more out of
ignorance than lack of care: I had not figured out how the homebrew formula
ran the configure script. Your help set me on the right path, however, and
I have solved the problem. Thank you!
For anyone else having this particular problem, a recapitulation: homebrew
recently decided to not allow install options for their core packages. That
means that pcre support is no longer available as an install option for
zsh. One thus has to modify the zsh formula and then install zsh from
source to include pcre. Here are the steps:
- "brew edit zsh". Add the lines: ' depends_on "pcre" ' and '
"--enable-pcre", ' to the formula. It should be obvious where they fit.
- "brew remove zsh"
- "brew install --build-from-source zsh"
prev parent reply other threads:[~2019-01-07 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190107135447epcas1p1ef8a8e73868d1d86f95e75acc64f7a4b@epcas1p1.samsung.com>
2019-01-07 13:52 ` Jesper Nygårds
2019-01-07 14:45 ` Peter Stephenson
2019-01-07 15:18 ` Jesper Nygårds
2019-01-07 15:41 ` Peter Stephenson
2019-01-07 19:37 ` Jesper Nygårds [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='CABZhJg9udPdFr4vvHLRTnSft5rLCr3CFGiwweE=5C1oeXjH_fg@mail.gmail.com' \
--to=jesper.nygards@gmail.com \
--cc=zsh-users@zsh.org \
/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).