From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: des@FreeBSD.org
Cc: Zsh Hackers' List <zsh-workers@sunsite.dk>
Subject: zsh 4.3.6 FreeBSD bug
Date: Sat, 3 May 2008 00:39:47 -0700 [thread overview]
Message-ID: <20080503073947.GA22661@redoubt.spodhuis.org> (raw)
Hi,
FreeBSD's conflict in definitions for wchar_t and wint_t if ncurses.h is
included with _XOPEN_SOURCE_EXTENDED defined (conflict with stddef.h and
wchar.h) means that zsh 4.3.6 fails to build on FreeBSD 6.2/amd64.
There's already logic in configure/configure.ac to handle OpenBSD
specially. If I just add *freebsd* to the OS check, zsh builds fine for
me. I don't know enough to know why this wasn't needed for you, unless
it only affects 64-bit.
I just hacked configure directly to avoid an autoconf rebuild.
----------------------------8< cut here >8------------------------------
--- configure.old Sat May 3 07:27:20 2008
+++ configure Sat May 3 07:27:53 2008
@@ -6880,7 +6880,7 @@
echo $ECHO_N "(cached) $ECHO_C" >&6
else
case "$host_os" in
- *openbsd*)
+ *openbsd*|*freebsd*)
zsh_cv_curses_needs_xopen=no
;;
*)
----------------------------8< cut here >8------------------------------
This _should_ do it for a rebuild case (untested).
----------------------------8< cut here >8------------------------------
--- configure.ac.old Sat May 3 07:34:09 2008
+++ configure.ac Sat May 3 07:34:24 2008
@@ -674,7 +674,7 @@
AC_CACHE_CHECK(if the curses library needs _XOPEN_SOURCE_EXTENDED,
zsh_cv_curses_needs_xopen,
[case "$host_os" in
- *openbsd*)
+ *openbsd*|*freebsd*)
zsh_cv_curses_needs_xopen=no
;;
*)
----------------------------8< cut here >8------------------------------
Regards,
-Phil
next reply other threads:[~2008-05-03 7:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 7:39 Phil Pennock [this message]
2008-05-04 12:08 ` Dag-Erling Smørgrav
2008-05-04 12:25 ` Dag-Erling Smørgrav
2008-05-05 22:02 ` Phil Pennock
2008-05-06 8:51 ` Peter Stephenson
2008-05-06 10:05 ` Dag-Erling Smørgrav
2008-05-06 9:11 ` Dag-Erling Smørgrav
2008-05-06 9:13 ` Dag-Erling Smørgrav
2008-05-06 9:24 ` Peter Stephenson
2008-05-06 10:24 ` Dag-Erling Smørgrav
2008-05-06 10:26 ` Peter Stephenson
2008-05-06 10:30 ` Dag-Erling Smørgrav
2008-05-06 10:42 ` Peter Stephenson
2008-05-06 11:51 ` Dag-Erling Smørgrav
2008-05-04 12:19 ` Peter Stephenson
2008-05-04 18:37 ` Peter Stephenson
2008-05-05 0:38 ` Phil Pennock
2008-05-05 0:41 ` Phil Pennock
2008-05-05 14:05 ` Peter Stephenson
2008-05-05 20:02 ` Jun T.
2008-05-06 2:32 ` Phil Pennock
2008-05-05 7:56 ` Dag-Erling Smørgrav
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=20080503073947.GA22661@redoubt.spodhuis.org \
--to=zsh-workers+phil.pennock@spodhuis.org \
--cc=des@FreeBSD.org \
--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).