bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem building gdb 6.3 with ncurses 5.4


From: Johnson, Drew
Subject: Problem building gdb 6.3 with ncurses 5.4
Date: Thu, 28 Apr 2005 09:52:26 -0400

Hello,

  I just attempted to build gdb V6.3 on Solaris10 using gcc v 3.3.2.  I also have ncurses 5.4 installed on that system, because vim 6.3 uses it.  Running configure and make yields the following errors:

In file included from tui/tui.c:48:

/usr/include/term.h:1060: error: parse error before "SGTTY"

/usr/include/term.h:1120: error: parse error before '}' token

/usr/include/term.h:1205: error: conflicting types for `putp'

/usr/local/include/ncurses/ncurses.h:658: error: previous declaration of `putp'

/usr/include/term.h:1207: error: conflicting types for `vidputs'

/usr/local/include/ncurses/ncurses.h:716: error: previous declaration of `vidputs'

In file included from tui/tui.c:48:

/usr/include/term.h:1209:31: macro "resetterm" passed 1 arguments, but takes just 0

/usr/include/term.h:1209:46: macro "fixterm" passed 1 arguments, but takes just 0

/usr/include/term.h:1209:62: macro "saveterm" passed 1 arguments, but takes just 0

 

Version 6.2 of gdb builds just fine on the same system using the same compiler and ncurses.  I noticed a difference in gdb/gdb_curses.h going from 6.2 to 6.3.

 

I have not done any further investigation of the cause of this, mostly because I can live with gdb 6.2.  I also wanted to see if this was already reported and maybe corrected.  If not, let me know and I can do more investigation and see if I can give you corrected versions of files I find necessary to change.

 

Drew Johnson

Andrew Corporation


------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender
immediately and delete the original. Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

reply via email to

[Prev in Thread] Current Thread [Next in Thread]