From: Steve Ellcey <sje@cup.hp.com>
To: UDOGAN@THY.COM
Cc: gdb@sources.redhat.com
Subject: Re: HPUX build error
Date: Wed, 08 Jun 2005 15:09:00 -0000 [thread overview]
Message-ID: <200506081509.IAA29433@hpsje.cup.hp.com> (raw)
In-Reply-To: <C53F9CF10BA3E748BE427B215AF5F8F1062D0363@TKMAIL01.thynet.thy.com>
> In file included from ./tui/tui.c:48:
> /usr/include/term.h:49: error: conflicting types for 'chtype'
> /usr/local/include/ncurses/ncurses.h:99: error: previous declaration of =
> 'chtype'
> was here
> /usr/include/term.h:64: error: conflicting types for 'attr_t'
I would blame the ncurses installation for having a different definition
of chtype. Since it is in /usr/local it is not the HP-UX system version
of curses. If I look in /usr/include/curses.h, it has the same
definition of chtype (and presumbably the other types) as
/usr/include/term.h so I would try to build gdb with the standard curses
package instead of with ncurses.
Another option would be to turn of the tui part of the build. I believe
gdb supports --disable-tui.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2005-06-08 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 8:32 UDOGAN
2005-06-08 15:09 ` Steve Ellcey [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 13:03 UDOGAN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506081509.IAA29433@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=UDOGAN@THY.COM \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox