Re: Newbie link problem: Error 1

On Sat, Nov 22, 2003 at 06:03:29PM -0800, [email protected] wrote:
> configure told me nothing of the kind that I can find.  I have re-run
> both config and make, after downloading libncurses-devel, and attached a
> copy of all of the output from running both configure and make in that

you did not restart from scratch so _some chached values_ are used
and thus the resulut is screwed up entirely (depending on what has
changed this might leadt e.g. to no error messages during
configure but compilation or linkage will fail). if you change your
system setup (installing a new library (version) you have to remove
the cached data from the last configure run first, e.g. via

	make distclean

or by manually removing some files:

	rm config.status config.cache src/Makefile include/autoconf.h 

> Show me where that warning (or anything even remotely like it) appears
> in configure's output.  Please.  I beg you.

show us the configure output of your first configure run (that one
which lead to the parsdate.y error). please. i beg you. in that run
(from clean data) both warnings were included.

> I didn't ignore any such message, unless you can point it out to me.

you did in the first two runs and then used cached data for the
configure run which screws up the result.

btw. you really should use tin-1.6.2 instead of tin-1.5.8 (as the
1.5.xer tree ever was a UNSTABLE development tree) and is heavily
outdated. and be sure you reread the available options for configure
(./configure --help) and look at doc/INSTALL to get some additional
infos about each available option. (I didn't check the 1.5.8er
configure script, but current versions do use
--with-screen=librarytype instead of --with-curses etc..p.)

btw. calling configure without any options usualy doesn't make much
sense as it's very unlikely that your system matches the default
configuration (e.g. I don't think you need local spool support (I
doubt that anyone runs a local newsserver with traditional spool
under cygwin) but only nntp support, when looking for errors it might
be a good idea to add --verbose, etc.pp).