public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: james_b_wexler@raytheon.com To: insight-gnats@sources.redhat.com Subject: insight/167: insight source files wont build :( Date: Fri, 21 Jun 2002 10:33:00 -0000 [thread overview] Message-ID: <20020621172855.10304.qmail@sources.redhat.com> (raw) >Number: 167 >Category: insight >Synopsis: insight source files wont build :( >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jun 21 10:33:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: james_b_wexler@raytheon.com >Release: all >Organization: >Environment: red hat linux box, 7.2 >Description: Ive downloaded the source for both insight 5.1.1 and 5.0 and it wont build in either case. the ./configure worked out fine and configured correctly but when i make i get this error: make[1]: Entering directory `/project/home/wexlerj/insight/insight-5.0/gdb' 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 -DGDBTK -DUSE_INCLUDED_REGEX utils.c In file included from /usr/include/curses.h:111, from utils.c:28: /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdbool.h:39: conflicting types for `false' ../bfd/bfd.h:101: previous declaration of `false' /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdbool.h:41: conflicting types for `true' ../bfd/bfd.h:101: previous declaration of `true' make[1]: *** [utils.o] Error 1 make[1]: Leaving directory `/project/home/wexlerj/insight/insight-5.0/gdb' make: *** [all-gdb] Error 2 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-21 17:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-21 10:33 james_b_wexler [this message] 2002-06-21 10:53 Keith Seitz 2002-08-28 17:13 kseitz
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=20020621172855.10304.qmail@sources.redhat.com \ --to=james_b_wexler@raytheon.com \ --cc=insight-gnats@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: linkBe 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).