public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Koundinya K <knk@dde.dk>
Cc: insight@sourceware.cygnus.com, gdb-patches@cygnus.com
Subject: Re: problems compiling Insight-20000204...
Date: Tue, 15 Feb 2000 23:50:00 -0000	[thread overview]
Message-ID: <38AA56A3.6F2D5BEA@cygnus.com> (raw)
In-Reply-To: <38A8A926.7939701D@dde.dk>

Koundinya K wrote:
> 
> hi all,
>     I am trying to compiler the snapshot of insight mentioned in the
> Subject to my mips based machine running SVR4.2 UNIX (
> mips-dde-sysv4.2MP).
> 
> Previously I was able to compile insight-19990928 and I have been using
> it for sometime now.
> 
> The error I get is.
> 
> "../../insight-20000204/gdb/proc-api.c", line 556: undefined symbol:
> BREAKPOINT
> "../../insight-20000204/gdb/proc-api.c", line 556: warning: {}-enclosed
> initializer required
> "../../insight-20000204/gdb/proc-api.c", line 556: non-constant
> initializer: op "NAME"
> make[1]: *** [proc-api.o] Error 1
> make[1]: Leaving directory `/gnu/debuggers/build-insight-20000204/gdb'
> make: *** [all-gdb] Error 2
> halfway:3919 2[/gnu/debuggers/build-insight-20000204]
> 
> Apparently this file proc-api.c is a new file, which I don't see in
> nsight-19990928. Like other targets BREAKPOINT should be defined in the
> relevant tm file . In my case tm-mipsv4.h. But this is not defined. Any
> pointers on what this could be defined as or atleast pointing me to the
> relevant docs could be helpful.
> 
> Thanks in advance for any help received.

Good find.

BREAKPOINT, BIG_BREAKPOINT, LITTLE_BREAKPOINT, ... have all been
deprecated in favour of BREAKPOINT_FROM_PC().  The MIPS is one of the
few targets providing just that interface.

The code will need to be changed so that it doesn't use BREAKPOINT. 
Anyone?

	Andrew

  reply	other threads:[~2000-02-15 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-14  9:16 Koundinya K
2000-02-15 23:50 ` Andrew Cagney [this message]
2000-02-16  1:24   ` Koundinya K

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=38AA56A3.6F2D5BEA@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=knk@dde.dk \
    /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).