[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Autoconf asks me to send a report

From: Peter Dyballa
Subject: Autoconf asks me to send a report
Date: Fri, 07 Nov 2003 22:14:12 +0100
User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007


During configuration of the Fink package python23-2.3.2-11 this happened:

checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking ncurses.h usability... no
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 address@hidden ##
configure: WARNING:     ## ------------------------------------ ##
checking for ncurses.h... yes
checking poll.h usability... no
checking poll.h presence... no
checking for poll.h... no

Configure was invoked this way:

./configure --prefix=/sw --mandir='${prefix}/share/man'

The autoconf version used is probably this one:

pete 164 /\ /sw/bin/autoconf --version
autoconf (GNU Autoconf) 2.57
Written by David J. MacKenzie and Akim Demaille.

My computer is an elder Apple PowerBook G4 with Mac OS X version 10.2.8, December 2002 Developer Tools and gcc version 3.3, make version: 3.79.

The C header file(s):

pete 160 /\ l /sw/include/ncurses/ncurses.h /usr/include/ncurses.h
lrwxr-xr-x 1 root 8 27. Oct 23:29 /sw/include/ncurses/ncurses.h -> curses.h lrwxr-xr-x 1 root 8 27. Oct 00:01 /usr/include/ncurses.h -> curses.h
pete 161 /\ l /sw/include/ncurses/curses.h /usr/include/curses.h
-rw-r--r--    1 root   55895 27. Oct 23:22 /sw/include/ncurses/curses.h
-rw-r--r--    1 root   54041  5. Nov 2002  /usr/include/curses.h

According to gcc invocation surely Fink's /sw/include/ncurses/curses.h was used instead of Apple's /usr/include/curses.h.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]