From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3118 invoked by alias); 7 May 2004 15:10:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3096 invoked from network); 7 May 2004 15:10:56 -0000 Received: from unknown (HELO tisch.mail.mindspring.net) (207.69.200.157) by sources.redhat.com with SMTP; 7 May 2004 15:10:56 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BM702-000396-00; Fri, 07 May 2004 11:10:55 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id CA6424B104; Fri, 7 May 2004 11:10:48 -0400 (EDT) To: kettenis@chello.nl, mec.gnu@mindspring.com Subject: Re: [patch] configure.in: revert osf5.1 no-noncurses special case Cc: gdb-patches@sources.redhat.com Message-Id: <20040507151048.CA6424B104@berman.michael-chastain.com> Date: Fri, 07 May 2004 15:10:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-05/txt/msg00199.txt.bz2 Hi Mark, Yeah, I was unhappy about reverting the patch, but in the long run, the problem is not really specific to osf5.1, so it's better to solve the real problem. > 4. Unly use ncurses if the user passes --with-ncurses to configure. I prefer this solution the best. We've had similar requests for readline from people who want to use the system readline library or their own readline library rather than our bundled readline. And this way a clueful user has the maximum usability, while a no-customization user has a good chance of getting a working gdb and even a gdbtui. > 1. Prefer a system's native curses library over ncurses. My second choice, because it's simple. > 2. Only use ncurses if we can find both the headers and the associated library. a. Error out if one of the parts if missing. b. Fall back on the system's native curses library if something is missing. > 3. Try harder to find all ncurses components by fiddling with CPPFLAGS and LDFLAGS. These are equally meh to me. I agree with your assessments of 2a, 2b, and 3. The advantage of the current scheme (option #0) is that it might work on some systems. I'm unhappy with #0 because I know that it doesn't work on my hp test drive system. As I understand it, you are unhappy with #1 for the converse reason: the configury can automatically make a bad choice on some systems. There are actually several flavors of 4: 4A. if --with-ncurses is not specified, always use curses 4B. if --with-ncurses is not specified, probe for ncurses automatically anyways I like 4A because it's simple and it gives full control. But it doesn't automatically work on some systems where a different plan would automatically work. Michael C