Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Jon Beniston'" <jon@beniston.com>,
	        "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Add support for the Lattice Mico32 (LM32) architecture
Date: Mon, 18 May 2009 15:57:00 -0000	[thread overview]
Message-ID: <004601c9d7d1$2cff5f00$86fe1d00$@u-strasbg.fr> (raw)
In-Reply-To: <ECAE046CAE6E452D962913D8ABFA9DB2@bibi>

Hi Jon,

your commit seems to have broken something:

cygwin compilation with --enable-targets=all
fails with this message.

I suspect that you have a local file name sim-lm32.h
that you forgot to add to cvs...
But I don't see it in the patches that you sent to the mailing
list either.

Could you please try to fix this?

Pierre Muller
Pascal language support maintainer for GDB


gcc -gstabs+ -O0   -I. -I../../purecvs/gdb -I../../purecvs/gdb/common
-I../../pu
recvs/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I../
../purecvs/gdb/../include/opcode -I../../purecvs/gdb/../readline/.. -I../bfd
-I.
./../purecvs/gdb/../bfd -I../../purecvs/gdb/../include -I../libdecnumber
-I../..
/purecvs/gdb/../libdecnumber  -I../../purecvs/gdb/gnulib -Ignulib
-DMI_OUT=1 -D
TUI=1   -Wall -Wdeclaration-after-statement -Wpointer-arith
-Wformat-nonliteral
-Wno-unused -Wno-switch -Wno-char-subscripts -Werror -c -o lm32-tdep.o -MT
lm32-
tdep.o -MMD -MP -MF .deps/lm32-tdep.Tpo ../../purecvs/gdb/lm32-tdep.c
../../purecvs/gdb/lm32-tdep.c:30:26: gdb/sim-lm32.h: No such file or
directory
../../purecvs/gdb/lm32-tdep.c: In function `lm32_register_reggroup_p':
../../purecvs/gdb/lm32-tdep.c:82: error: `SIM_LM32_R0_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:82: error: (Each undeclared identifier is
reported
 only once
../../purecvs/gdb/lm32-tdep.c:82: error: for each function it appears in.)
../../purecvs/gdb/lm32-tdep.c:82: error: `SIM_LM32_RA_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:83: error: `SIM_LM32_PC_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:85: error: `SIM_LM32_EA_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:85: error: `SIM_LM32_BA_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:86: error: `SIM_LM32_EID_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:86: error: `SIM_LM32_IP_REGNUM' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_cannot_store_register':
../../purecvs/gdb/lm32-tdep.c:122: error: `SIM_LM32_R0_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:122: error: `SIM_LM32_EID_REGNUM' undeclared
(firs
t use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_analyze_prologue':
../../purecvs/gdb/lm32-tdep.c:143: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:160: error: `SIM_LM32_FP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:166: error: `SIM_LM32_R0_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_skip_prologue':
../../purecvs/gdb/lm32-tdep.c:190: error: `SIM_LM32_NUM_REGS' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_push_dummy_call':
../../purecvs/gdb/lm32-tdep.c:237: error: `SIM_LM32_R1_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:242: error: `SIM_LM32_RA_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:299: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_extract_return_value':
../../purecvs/gdb/lm32-tdep.c:320: error: `SIM_LM32_R1_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:328: error: `SIM_LM32_R2_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_store_return_value':
../../purecvs/gdb/lm32-tdep.c:353: error: `SIM_LM32_R1_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:360: error: `SIM_LM32_R2_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_unwind_pc':
../../purecvs/gdb/lm32-tdep.c:390: error: `SIM_LM32_PC_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_unwind_sp':
../../purecvs/gdb/lm32-tdep.c:396: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_dummy_id':
../../purecvs/gdb/lm32-tdep.c:402: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_frame_cache':
../../purecvs/gdb/lm32-tdep.c:440: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:455: error: `SIM_LM32_PC_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:455: error: `SIM_LM32_RA_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c: In function `lm32_gdbarch_init':
../../purecvs/gdb/lm32-tdep.c:543: error: `SIM_LM32_NUM_REGS' undeclared
(first
use in this function)
../../purecvs/gdb/lm32-tdep.c:544: error: `SIM_LM32_SP_REGNUM' undeclared
(first
 use in this function)
../../purecvs/gdb/lm32-tdep.c:545: error: `SIM_LM32_PC_REGNUM' undeclared
(first
 use in this function)
make[1]: *** [lm32-tdep.o] Error 1
make[1]: Leaving directory `/usr/local/src/gdbcvs/multibuild/gdb'
make: *** [all-gdb] Error 2

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Jon Beniston
> Envoyé : Wednesday, May 13, 2009 4:49 PM
> À : 'Joel Brobecker'
> Cc : gdb-patches@sourceware.org
> Objet : RE: [PATCH] Add support for the Lattice Mico32 (LM32)
> architecture
> 
> Hi,
> 
> > Perfect. So it seems that all portions of your code have been
> > approved, and you can commit. Right?
> 
> How do I get write access to CVS? Is the account name picked up from
> the MAINTAINERS file?
> 
> If so, attached is a patch for MAINTAINERS.
> 
> Cheers,
> Jon
> 
> 2009-05-13  Jon Beniston  <jon@beniston.com>
> 
> 	* MAINTAINERS: Add Jon Beniston to write after approval list.


  parent reply	other threads:[~2009-05-18 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 12:06 Jon Beniston
2009-02-07  4:14 ` Joel Brobecker
2009-04-15 18:09   ` Jon Beniston
2009-04-15 19:24     ` Eli Zaretskii
2009-05-07 16:49     ` Joel Brobecker
2009-05-07 18:35       ` Eli Zaretskii
2009-05-07 23:13       ` Jon Beniston
2009-05-08 15:32         ` Joel Brobecker
2009-05-11 16:24           ` Jon Beniston
2009-05-11 16:39             ` Joel Brobecker
2009-05-13 14:49               ` Jon Beniston
2009-05-13 15:29                 ` Joel Brobecker
2009-05-18 15:57                 ` Pierre Muller [this message]
2009-05-18 16:09                   ` Pierre Muller
  -- strict thread matches above, loose matches on Subject: below --
2008-12-16  0:52 Jon Beniston

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='004601c9d7d1$2cff5f00$86fe1d00$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jon@beniston.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