zsh-workers
 help / color / mirror / code / Atom feed
From: Motoi Washida <a66@h8.dion.ne.jp>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: 4.2.4 failure on MacOS X
Date: Fri, 4 Feb 2005 04:01:02 +0900	[thread overview]
Message-ID: <a2cd090851702fd1519fbabaa1e3ab4f@h8.dion.ne.jp> (raw)
In-Reply-To: <200502031615.j13GFnuc005915@news01.csr.com>

I also failed to build zsh on Mac OS X 10.3.7.

I think this is because configure can't find iconv(), because iconv() 
is defined as libiconv() in /usr/include/iconv.h and the configure 
script checks iconv() without using the header file.

I modified configure.ac a bit and seems to work. Here is the patch.

--
Motoi Washida



Index: configure.ac
===================================================================
RCS file: /cvsroot/zsh/zsh/configure.ac,v
retrieving revision 1.25
diff -d -u -r1.25 configure.ac
--- configure.ac	1 Feb 2005 10:53:10 -0000	1.25
+++ configure.ac	3 Feb 2005 18:42:05 -0000
@@ -729,10 +729,11 @@

  AC_CHECK_LIB(iconv, iconv)

-if test "$host_os" = cygwin; then
-dnl cygwin iconv() is really libiconv()
-AC_CHECK_LIB(iconv, libiconv)
-fi
+case "$host_os" in
+  cygwin | darwin*)
+    dnl cygwin iconv() is really libiconv()
+    AC_CHECK_LIB(iconv, libiconv) ;;
+esac

  if test x$enable_pcre = xyes; then
  dnl pcre-config should probably be employed here


  parent reply	other threads:[~2005-02-03 19:02 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
2005-02-03 17:19   ` Peter Stephenson
2005-02-04 18:55     ` Peter A. Castro
2005-02-03 19:01 ` Motoi Washida [this message]
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=a2cd090851702fd1519fbabaa1e3ab4f@h8.dion.ne.jp \
    --to=a66@h8.dion.ne.jp \
    --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).