From: Andrew Cagney <ac131313@redhat.com>
To: Mike Cleary <mcleary@iol.unh.edu>
Cc: gdb@sources.redhat.com, clp <clp@iol.unh.edu>
Subject: Re: gdb make error
Date: Fri, 18 Oct 2002 15:40:00 -0000 [thread overview]
Message-ID: <3DB08DCF.3060308@redhat.com> (raw)
In-Reply-To: <3DA2DA7A.3020306@iol.unh.edu>
> Greetings,
> I have found the following make error for gdb on an alpha with the alphaev56 configuration the basic-gcc_2.95.3 baseline and the toolchain package:
Which exact GDB? (What is the contents of src/gdb/version.in?)
If you can't build a gdb from
ftp://sources.redhat.com/pub/gdb/snapshots/branch/ (the 5.3 branch) then
this is a concern and a bug report would be appreciated
(http://sources.redhat.com/gdb/bugs) (although a simple patch would be
appreciated more ;-).
Andrew
> gcc -c -g -O2 -I. -I/mnt/u9/toolchain/buildsys/source/toolchain/gdb -I/mnt/u9/toolchain
> /buildsys/source/toolchain/gdb/config -DLOCALEDIR="\"/mnt/u9/toolchain/buildsys/install/al
> pha9/basic-gcc_2.95.3/native/toolchain/share/locale\"" -DHAVE_CONFIG_H -I/mnt/u9/toolchain
> /buildsys/source/toolchain/gdb/../include/opcode -I/mnt/u9/toolchain/buildsys/source/toolc
> hain/gdb/../readline/.. -I../bfd -I/mnt/u9/toolchain/buildsys/source/toolchain/gdb/../bfd -DNO_MMALLOC -I/mnt/u9/toolchain/buildsys/source/toolchain/gdb/../include -I../intl -I/mn
> t/u9/toolchain/buildsys/source/toolchain/gdb/../intl -DMI_OUT=1 -DGDBTK -DUI_OUT=1 -Wimpl
> icit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitia
> lized /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c: In function `resume':
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:873: parse error before `)'
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:881: `resume_ptid' undeclared (fi
> rst use in this function)
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:881: (Each undeclared identifier is reported only once
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:881: for each function it appears
> in.)
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c: At top level:
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:884: warning: type defaults to `i
> nt' in declaration of `discard_cleanups'
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:884: warning: parameter names (wi
> thout types) in function declaration
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:884: conflicting types for `disca
> rd_cleanups'
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/defs.h:331: previous declaration of `disca
> rd_cleanups'
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:884: warning: data definition has
> no type or storage class
> /mnt/u9/toolchain/buildsys/source/toolchain/gdb/infrun.c:885: parse error before `}'
> make[2]: *** [infrun.o] Error 1
> make[2]: Leaving directory `/mnt/u9/toolchain/buildsys/build/alpha9/basic-gcc_2.95.3/nativ
> e/toolchain/gdb'
> make[1]: *** [all-gdb] Error 2
> make[1]: Leaving directory `/mnt/u9/toolchain/buildsys/build/alpha9/basic-gcc_2.95.3/nativ
> e/toolchain'
> make: *** [bootstrap] Error 2
>
> I was wondering if anyone can help me with this.
> Salutations,
> -Mike
>
> --
> ***********************************************
> Michael Cleary Email: mcleary@iol.unh.edu
> UNH InterOperability Lab Linux Group
> 121 Technology Dr., Suite 2, Durham, NH 03824
> Phone: 603-862-0401 http://linux.iol.unh.edu
> ***********************************************
>
>
>
next prev parent reply other threads:[~2002-10-18 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 6:12 Mike Cleary
2002-10-18 15:40 ` Andrew Cagney [this message]
2002-10-18 12:26 Mike Cleary
2002-10-18 12:34 ` Daniel Jacobowitz
2002-12-03 6:22 Mike Cleary
2002-12-05 13:44 Mike Cleary
2002-12-06 11:47 Mike Cleary
2002-12-06 15:04 ` bemis
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=3DB08DCF.3060308@redhat.com \
--to=ac131313@redhat.com \
--cc=clp@iol.unh.edu \
--cc=gdb@sources.redhat.com \
--cc=mcleary@iol.unh.edu \
/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