Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <39136085.60329B3@pacbell.net> Date: Fri, 05 May 2000 17:00:05 -0700 From: Jay Bromley X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: building gdb 4.18 w/ net cygwin 1.1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello there! I recently installed the latest net cygwin 1.1.0 and everything worked great except for gdb. When I run gdb the UI (Insight I guess) reports an internal gdb error and asks if I wish to continue. Continuing only results in a whole stream of such errors making gdb unusable. I then fetched the latest gdb-4.18 source from ftp.gnu.org and attempted to build it in the following manner (both done from the top level gdb-4.18 directory): ./configure i686-pc-cygwin32 make Now, i686-pc-cygwin32 is what is reported by ./config.guess and the configuration goes off without a hitch. However, the make chokes while compiling win32-nat.c with the following message: gcc -c -g -O2 -I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode -I./.. /readline/.. -I../bfd -I./../bfd -I./../include -I../intl -I./../intl -I./tui win32-nat.c win32-nat.c: In function `thread_rec': win32-nat.c:185: `CONTEXT_DEBUGGER' undeclared (first use in this function) win32-nat.c:185: (Each undeclared identifier is reported only once win32-nat.c:185: for each function it appears in.) win32-nat.c: In function `child_resume': win32-nat.c:967: `FLAG_TRACE_BIT' undeclared (first use in this function) make[1]: *** [win32-nat.o] Error 1 make[1]: Leaving directory `/usr/local/src/gdb-4.18/gdb' make: *** [all-gdb] Error 2 I gripped the gdb sources and failed to find either CONTEXT_DEBUGGER or FLAG_TRACE_BIT and could find neither. I also grepped my MSVC directories to see if perhaps something got left out of a cygwin header but no luck there either. So the question: has anyone successfully built gdb-4.18 with the latest (unmodified) net cygwin 1.1.0? (I assume someone has, gdb being such a vital tool and me having seen lots of people on the mailing list at least able to build gdb on the mailing list.) I am running NT 4.0 SP6 and using a completely unmodified net cygwin package (just installed yesterday.) I have been able to build a number of other GNU packages with success. Any hints would be appreciated as I *really* need a debugger right about now. I did not include cygcheck -r -s -v due to its length but if anyone thinks it might be a config issue I would be glad to post it. Thanks and regards, Jay Bromley jaywb AT pacbell DOT net -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com