Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <5.1.0.14.1.20020106185210.00a79aa0@pop.erols.com> X-Sender: prapp@pop.erols.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 06 Jan 2002 19:01:34 -0500 To: cygwin@sources.redhat.com From: prapp Subject: Re: system details on my little ncurses struggles In-Reply-To: <3C38D9EC.2030307@ece.gatech.edu> References: <5.1.0.14.1.20020106175325.00a7dec0@pop.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Ok, I'm leaving the subject line as is, but changing the headers so this goes to the list instead of you personally (the from was you and there was no Reply-To). Hopefully this is the correct thing to do. >searched the archives. The current version of ncurses, 5.2-7, requires >that you -DBROKEN_LINKER for both -static and dynamic builds. Try >compiling with -DBROKEN_LINKER, but link dynamically (without -static) >A-ha! This is the BROKEN_LINKER problem. >Try to link dynamically with -DBROKEN_LINKER first. Then we can >investigate wacky COLS gdb problems. Yes! If I define BROKEN_LINKER, I can compile & then successfully link either way (with or without -static). I find it still crashes under gdb if linked without -static (segfault at the first reference to LINES), but if both compiled with BROKEN_LINKER and linked with -static, then it runs under gdb without segfaulting. Thanks much! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/