On Mon, Apr 23, 2001 at 04:00:29PM -0500, Stephen Dickey wrote:
From: Stephen Dickey <stephendickey(a)finchcms.edu>
Subject: configure panic
I am having a problem similar to something I saw on this
*** PANIC *** The C compiler can no longer build working executables.
*** PANIC *** Please examine the tail of config.log for runtime errors.
*** PANIC *** The most likely reason for this problem is that configure
*** PANIC *** links with shared libraries, but those libraries cannot be
*** PANIC *** found at run time.
*** PANIC ***
*** PANIC *** On a Linux system, edit /etc/ld.so.conf and re-run ldconfig.
*** PANIC *** On other systems, try telling configure where to find the
*** PANIC *** shared libraries using the --site-runtime-libraries option
*** PANIC ***
*** PANIC *** Another way to shoot yourself in the foot is to specify
*** PANIC *** --with-FEATURE when FEATURE is not actually installed
*** PANIC *** on your system. Don't do that.
this is on a linux from scratch system which deffinately has ncurses
and does not have termcap. I'm not sure when this broke but everything was
building fine a couple of weeks ago.
here is what seems to be the relevant portion of config.log:
configure:13267: checking for TTY-related features
configure:13283: checking for tgetent in -lncurses
configure:13299: gcc -o conftest -g -O3 -Wall -Wno-switch -Winline
-Wmissing-prototypes -Wshadow -Wsign-compare -I/usr/X11R6/include
-L/usr/X11R6/lib conftest.c -lncurses -lXmu -lXt -lXext -lX11 -lSM
-lICE -lm -lshell32 -lgdi32 -luser32 -lcomdlg32 -lcomctl32 -lwinspool -lgcc
-lc -lgcc /usr/lib/crtn.o 1>&5
/usr/bin/ld: cannot find -lwinspool
Here's the problem ^^^^^^^^^^^, it cannot find winspool so it assumes
you don't have ncurses...
Definitely a win32 type problem so I can't offer much else.
<SNIP long configure.log>