Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Type cleanups
Date: Mon, 13 May 2002 08:51:00 -0000	[thread overview]
Message-ID: <15583.57551.427061.541618@localhost.redhat.com> (raw)
In-Reply-To: <3CDFDDB9.7020904@cygnus.com>

Andrew Cagney writes:
 > 
 > >> Did you check all the cross targets build per MAINTAINERS?  From memory 
 > >> sh-hms[bfd] and avr[need to look] don't build at present (well as of 
 > >> ~2002-05-12-gmt).
 > >> 
 > >> If that has been checked, then yes ``obviously''.
 > > 
 > > 
 > > A few don't build; none of them are my fault.  For the record:
 > > 
 > > 	At least fr30-elf, mn10300-elf, and v850-elf have missing
 > > dependencies off in sim/ land; they built with non-parallel make only.
 > 
 > > 	hppa1.1-hp-proelf wants dl.h and machine/save_state.h in
 > > hppa-tdep.c, and was already marked broken.  The nice gawk segment
 > > doesn't notice that...
 > 
 > HP/UX isn't on the list.  I get:
 > 
 > hppa1.1-hp-proelf broken
 > 
 > The note should probably mention that you normally want to stip out 
 > broken targets.
 > 
 > > 	Several targets (i586-pc-msdosdjgpp, sparc-elf, sparc64-elf)
 > > 	failed with this message (also JB_SP for Sparc):
 > > 
 > > In file included from /usr/include/setjmp.h:30,
 > >                  from ../../src-build/gdb/top.c:58:
 > > /usr/include/bits/setjmp.h:31: warning: `JB_PC' redefined
 > > tm.h:57: warning: this is the location of the previous definition
 > > make[1]: *** [top.o] Error 1
 > 
 > I don't get that on the three systems I use.  Bug in the system library?
 > 
 > > 
 > > 	sh-hms failed with a reference to some new SHmedia code.
 > 
 > Yes, per above, BFD problem.  sh-hms doesn't enable full SH support in BFD.
 > 

Yes.
I am looking into this right now.
Elena


 > Andrew
 > 
 > 
 > 
 > 
 > 


  reply	other threads:[~2002-05-13 15:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40   ` Daniel Jacobowitz
2002-05-12 21:31     ` Andrew Cagney
2002-05-13 11:46       ` Daniel Jacobowitz
2002-05-13 12:54         ` Daniel Berlin
2002-05-13 12:57           ` Daniel Jacobowitz
2002-05-13  6:59   ` Daniel Jacobowitz
2002-05-13  8:37     ` Andrew Cagney
2002-05-13  8:51       ` Elena Zannoni [this message]
2002-05-13  9:11         ` Andrew Cagney
2002-05-13  9:19           ` Elena Zannoni
2002-05-13 11:50       ` Daniel Jacobowitz
2002-05-13 11:59         ` Daniel Jacobowitz
2002-05-13 15:14           ` Andrew Cagney
2002-05-13 16:09             ` Daniel Jacobowitz
2002-05-13 18:37               ` Elena Zannoni
2002-05-14 17:09               ` Andrew Cagney
2002-05-17  1:11     ` Eli Zaretskii
2002-05-17  8:02       ` Daniel Jacobowitz
2002-05-17  9:14         ` Eli Zaretskii
2002-05-17 10:21           ` Daniel Jacobowitz
2002-05-17 10:34             ` Andrew Cagney
2002-05-18  0:15               ` Eli Zaretskii
2002-05-18  0:13             ` Eli Zaretskii

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=15583.57551.427061.541618@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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