From: "Peter A. Castro" <doctor@fruitbat.org>
To: Clint Adams <clint@zsh.org>
Cc: Peter Stephenson <pws@csr.com>,
Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: 4.2.4 failure on MacOS X
Date: Fri, 4 Feb 2005 10:59:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0502041055240.17079@ming.fruitbat.org> (raw)
In-Reply-To: <20050203183215.GA691@scowler.net>
On Thu, 3 Feb 2005, Clint Adams wrote:
> > Could be similar, but I don't think it's quite that. I can see libiconv
> > in /sw/lib on ppc-sx2.cf.sourceforge.net, but there's no pcre there.
> > -liconv should presumably be present to get it to link properly; the
>
> Be careful, there are at least three iconv's for MacOS X:
> - GNU iconv, which Fink would have installed into /sw/lib
> - maciconv
> - Apple's iconv, which is bundled with MacOS X 10.3 and presumably later
> versions.
But which one is the correct one to use? Are they all compatable with
each other and the compiler/runtime being use to build zsh? Do they all
have an iconv.h header (and if so, how/where)? I think a little better
detection in configure might be appropriate here, but without a Mac OS-X
environment it's difficult to discern this.
Perhaps it would be good for configure to #undef HAVE_ICONV_H if the
library isn't found?
> I think all three dynamic objects share the same name.
--
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
next prev parent reply other threads:[~2005-02-04 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 16:15 Peter Stephenson
2005-02-03 16:28 ` Bart Schaefer
2005-02-03 17:10 ` Peter Stephenson
2005-02-03 18:32 ` Clint Adams
2005-02-04 18:59 ` Peter A. Castro [this message]
2005-02-03 17:19 ` Peter Stephenson
2005-02-04 18:55 ` Peter A. Castro
2005-02-03 19:01 ` Motoi Washida
2005-02-04 10:35 ` Peter Stephenson
2005-02-04 19:10 ` Peter A. Castro
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=Pine.LNX.4.58.0502041055240.17079@ming.fruitbat.org \
--to=doctor@fruitbat.org \
--cc=clint@zsh.org \
--cc=pws@csr.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).