* HPUX build error
@ 2005-06-07 8:32 UDOGAN
2005-06-08 15:09 ` Steve Ellcey
0 siblings, 1 reply; 3+ messages in thread
From: UDOGAN @ 2005-06-07 8:32 UTC (permalink / raw)
To: gdb
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: HPUX build error
2005-06-07 8:32 HPUX build error UDOGAN
@ 2005-06-08 15:09 ` Steve Ellcey
0 siblings, 0 replies; 3+ messages in thread
From: Steve Ellcey @ 2005-06-08 15:09 UTC (permalink / raw)
To: UDOGAN; +Cc: gdb
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* HPUX build error
@ 2005-06-06 13:03 UDOGAN
0 siblings, 0 replies; 3+ messages in thread
From: UDOGAN @ 2005-06-06 13:03 UTC (permalink / raw)
To: gdb
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-08 15:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-07 8:32 HPUX build error UDOGAN
2005-06-08 15:09 ` Steve Ellcey
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 13:03 UDOGAN
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).