problems compiling Insight-20000204...

problems compiling Insight-20000204...

[Koundinya K]

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.

With best regards

Koundinya

Re: problems compiling Insight-20000204...

[Andrew Cagney]

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

Re: problems compiling Insight-20000204...

[Koundinya K]

hi all,
    At last my mail was answered. Thanks for that. Yup, I did some dirty
hack and got insight compiled. But I will look into this.

Thanks

Koundinya

Andrew Cagney wrote:

> 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