[Python-bugs-list] [ python-Bugs-811028 ] configure: curses busted
on Freebsd/Mac OSX
SourceForge.net
noreply at sourceforge.net
Tue Sep 30 19:29:10 EDT 2003
Bugs item #811028, was opened at 2003-09-23 17:50
Message generated for change (Comment added) made by richard
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=811028&group_id=5470
Category: Build
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Jones (richard)
Assigned to: Nobody/Anonymous (nobody)
Summary: configure: curses busted on Freebsd/Mac OSX
Initial Comment:
Anthony said to log this:
checking ncurses.h presence... yes
configure: WARNING: ncurses.h: present but cannot be
compiled
configure: WARNING: ncurses.h: check for missing
prerequisite headers?
configure: WARNING: ncurses.h: proceeding with the
preprocessor's result
configure: WARNING: ##
------------------------------------ ##
configure: WARNING: ## Report this to bug-
autoconf at gnu.org. ##
configure: WARNING: ##
------------------------------------ ##
I'll attach the text of the report and the configure output
too since I'm pretty sure the above won't be ligible once
sf's tracker's finished with it.
----------------------------------------------------------------------
>Comment By: Richard Jones (richard)
Date: 2003-10-01 09:29
Message:
Logged In: YES
user_id=6405
The diagnosis on OS X is similar, and the trigger for defining wchar_t in
stdlib.h is the absence of _ANSI_SOURCE.
Making it not define _XOPEN_SOURCE_EXTENDED also fixes the compile
as per your FreeBSD fix.
----------------------------------------------------------------------
Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-10-01 00:24
Message:
Logged In: YES
user_id=29957
Looking into it a bit on FreeBSD:
/usr/include/ncurses.h:236: conflicting types for `wchar_t'
/usr/include/stdlib.h:58: previous declaration of `wchar_t'
and poking around a bit I find that stdlib.h defines wchar_t
as an 'int', while ncurses.h defines it as 'unsigned long'.
This is on FreeBSD 4.8.
Extracting the failing configure code and making it not
define _XOPEN_EXTENDED_SOURCE makes the test succeed, but I
have no idea if this is an appropriate fix.
----------------------------------------------------------------------
Comment By: Richard Jones (richard)
Date: 2003-09-27 18:36
Message:
Logged In: YES
user_id=6405
(I didn't mention it in the report, only to Anthony : this is on
OSX)
The patch doesn't alter the configure behaviour.
I can't remember how to run the curses test - "make test" skips
it (the curses module is built though).
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2003-09-27 17:53
Message:
Logged In: YES
user_id=21627
Can you try the patch in python.org/sf/806800 ?
----------------------------------------------------------------------
Comment By: Richard Jones (richard)
Date: 2003-09-23 18:28
Message:
Logged In: YES
user_id=6405
"make test" also reports:
test_curses
test test_curses crashed -- _curses.error: curs_set() returned
ERR
----------------------------------------------------------------------
Comment By: Anthony Baxter (anthonybaxter)
Date: 2003-09-23 18:14
Message:
Logged In: YES
user_id=29957
creosote (which is a freebsd machine) also sees this.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=811028&group_id=5470
More information about the Python-bugs-list
mailing list