Re: [patch] configure.in: revert osf5.1 no-noncurses special case

[Mark Kettenis <kettenis@chello.nl>]

   Date: Fri,  7 May 2004 11:52:27 -0400 (EDT)
   From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
   > Personally, I don't see the point in worrying about this.  If you've got
   > a broken ncurses installation - one where the linker finds -lncurses but
   > gcc doesn't, or vice versa, is broken in my book - it's your problem.

   Right now I have *no way to fix it*.  I built ncurses 5.2, ncurses 5.3,
   and ncurses 5.4 on this system, and I built gdbtui with each of them and
   ran each of them.  All of them work.  But I had to hack the Makefile to
   do it, because there is no configuration option to tell gdb to use
   $MIGCHAIN_DIR_INSTALL/host/ncurses-5.4.  (And I can't install any
   software as root on this system).

   Suppose I want to test a new version of ncurses?

   Suppose I have an oddball platform and I need to patch ncurses in
   order to use it?

The way this is supposed to work with autoconf is that you set the
right environment variables (CPPFLAGS, LDFLAGS) before running
configure.  Unfortunately most configure scripts out there don't
respect these variables, because folks overide these variables in
their Makefile.in.