From: Mike Cleary <mcleary@iol.unh.edu>
To: gdb@sources.redhat.com
Cc: clp@iol.unh.edu
Subject: gdb make error
Date: Tue, 03 Dec 2002 06:22:00 -0000 [thread overview]
Message-ID: <3DECBE7D.40209@iol.unh.edu> (raw)
Greetings,
I have found the following make error for gdb on an alpha with the
alphaev56 configuration. I found the error with the basic-gcc_2.95.3
baseline and the toolchain package:
gcc -c -g -O2 -I. -I/mnt/u9/toolchain/buildsys/source/toolchain/gdb
-I/mnt/u9/tool
chain/buildsys/source/toolchain/gdb/config
-DLOCALEDIR="\"/mnt/u9/toolchain/buildsys/
install/alpha9/basic-gcc_2.95.3/native/toolchain/share/locale\""
-DHAVE_CONFIG_H -I/m
nt/u9/toolchain/buildsys/source/toolchain/gdb/../include/opcode
-I/mnt/u9/toolchain/b
uildsys/source/toolchain/gdb/../readline/.. -I../bfd
-I/mnt/u9/toolchain/buildsys/sou
rce/toolchain/gdb/../bfd -DNO_MMALLOC
-I/mnt/u9/toolchain/buildsys/source/toolchain/
gdb/../include -I../intl
-I/mnt/u9/toolchain/buildsys/source/toolchain/gdb/../intl -D
_BSD_SOURCE -D_XOPEN_SOURCE=500 -D_LARGEFILE64_SOURCE -DMI_OUT=1
-DGDBTK -DUI_OUT=1
-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses
-Wpointer-arith
-Wuninitialized p-exp.tab.c
/mnt/u9/toolchain/buildsys/source/toolchain/gdb/p-exp.y:183: warning:
`TRUE' redefine
d
../bfd/bfd.h:93: warning: this is the location of the previous definition
/mnt/u9/toolchain/buildsys/source/toolchain/gdb/p-exp.y:184: warning:
`FALSE' redefin
ed
../bfd/bfd.h:92: warning: this is the location of the previous definition
/mnt/u9/toolchain/buildsys/source/toolchain/gdb/p-exp.y:144: parse error
before `1'
make[2]: *** [p-exp.tab.o] Error 1
make[2]: Leaving directory
`/mnt/u9/toolchain/buildsys/build/alpha9/basic-gcc_2.95.3/
native/toolchain/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory
`/mnt/u9/toolchain/buildsys/build/alpha9/basic-gcc_2.95.3/
native/toolchain'
make: *** [bootstrap] Error 2
I was just wondering if anyone can help with this.
Salutations,
-Mike Cleary
--
*********************************************
Michael Cleary Email: mcleary@iol.unh.edu
Linux Consortium UNH InterOperability Lab
121 Technology Dr., Suite 2, Durham, NH 03824
Phone: 603-862-0401 http://www.iol.unh.edu
http://linux.iol.unh.edu/
*********************************************
next reply other threads:[~2002-12-03 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 6:22 Mike Cleary [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 11:47 Mike Cleary
2002-12-06 15:04 ` bemis
2002-12-05 13:44 Mike Cleary
2002-10-18 12:26 Mike Cleary
2002-10-18 12:34 ` Daniel Jacobowitz
2002-10-08 6:12 Mike Cleary
2002-10-18 15:40 ` Andrew Cagney
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=3DECBE7D.40209@iol.unh.edu \
--to=mcleary@iol.unh.edu \
--cc=clp@iol.unh.edu \
--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