From: <UDOGAN@THY.COM>
To: <gdb@sources.redhat.com>
Subject: HPUX build error
Date: Tue, 07 Jun 2005 08:32:00 -0000 [thread overview]
Message-ID: <C53F9CF10BA3E748BE427B215AF5F8F1062D0363@TKMAIL01.thynet.thy.com> (raw)
Hi,
We got the following error while building gdb 6.3 in hpux.
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'
/usr/local/include/ncurses/ncurses.h:285: error: previous declaration of 'attr_t
' was here
/usr/include/term.h:1217: error: conflicting types for 'tparm'
/usr/local/include/ncurses/ncurses.h:710: error: previous declaration of 'tparm'
was here
/usr/include/term.h:1217: error: conflicting types for 'tparm'
/usr/local/include/ncurses/ncurses.h:710: error: previous declaration of 'tparm'
was here
gmake[1]: *** [tui.o] Error 1
gmake[1]: Leaving directory `/home/umitd/gdb-6.3/gdb'
gmake: *** [all-gdb] Error 2
We run ./configure as;
$ ./configure --target=hppa64-hp-hpux11.11 --host=hppa64-hp-hpux11.11
creating cache ./config.cache
checking host system type... hppa64-hp-hpux11.11
checking target system type... hppa64-hp-hpux11.11
checking build system type... hppa64-hp-hpux11.11
checking for a BSD compatible install... ./install-sh -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for gnatbind... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp $$f1 $$f2 16 16
checking for correct version of gmp.h... no
checking for bison... no
checking for bison... no
checking for byacc... no
checking for yacc... yacc
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... no
checking for flex... no
checking for lex... lex
checking for makeinfo... no
checking for hppa64-hp-hpux11.11-ar... no
checking for ar... ar
checking for hppa64-hp-hpux11.11-as... no
checking for as... as
checking for hppa64-hp-hpux11.11-dlltool... no
checking for dlltool... dlltool
checking for hppa64-hp-hpux11.11-ld... /usr/ccs/bin/ld
checking for hppa64-hp-hpux11.11-nm... no
checking for nm... nm
checking for hppa64-hp-hpux11.11-ranlib... no
checking for ranlib... ranlib
checking for hppa64-hp-hpux11.11-windres... no
checking for windres... windres
checking for hppa64-hp-hpux11.11-objcopy... no
checking for objcopy... objcopy
checking for hppa64-hp-hpux11.11-objdump... no
checking for objdump... objdump
checking for hppa64-hp-hpux11.11-ar... no
checking for ar... ar
checking for hppa64-hp-hpux11.11-as... no
checking for as... as
checking for hppa64-hp-hpux11.11-dlltool... no
checking for dlltool... dlltool
checking for hppa64-hp-hpux11.11-ld... no
checking for ld... ld
checking for hppa64-hp-hpux11.11-nm... no
checking for nm... nm
checking for hppa64-hp-hpux11.11-ranlib... no
checking for ranlib... ranlib
checking for hppa64-hp-hpux11.11-windres... no
checking for windres... windres
checking whether to enable maintainer-specific portions of Makefiles... no
checking if symbolic links between directories work... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
Thanks for urgent help...
=============================================================================================
Bu e-mail mesaji ve ekleri, isimleri yazili alicilar disindaki kisilere aciklanmamasi, dagitilmamasi ve iletilmemesi gereken kisiye ozel ve gizli bilgiler icerebilir. Mesajin muhatabi degilseniz lutfen gonderici ile irtibat kurunuz, mesaj ve eklerini siliniz. E-mail sistemlerinin tasidigi guvenlik risklerinden dolayi, mesajlarin gizlilikleri ve butunlukleri bozulabilir, mesaj virus icerebilir. Bilinen viruslere karsi kontrolleri yapilmis olarak yollanan mesajin sisteminizde yaratabilecegi olasi zararlardan Sirketimiz (T.H.Y. A.O.) sorumlu tutulamaz.
This email and its attachments may contain private and confidential information intended for the use of the addressee only, which should not be announced, copied or forwarded. If you are not the intended recipient, please contact the sender, delete the message and its attachments. Due to security risks of email systems, the confidentiality and integrity of the message may be damaged, the message may contain viruses. This message is scanned for known viruses and our Company (Turkish Airlines Inc.) will not be liable for possible system damages caused by the message.
next reply other threads:[~2005-06-07 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 8:32 UDOGAN [this message]
2005-06-08 15:09 ` Steve Ellcey
-- 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=C53F9CF10BA3E748BE427B215AF5F8F1062D0363@TKMAIL01.thynet.thy.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).