Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA 2nd] remote-*.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr,...
Date: Mon, 29 Apr 2002 04:02:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20020429123751.00a75708@ics.u-strasbg.fr> (raw)
In-Reply-To: <3CC9521C.3080700@cygnus.com>

At 15:11 26/04/2002 , Andrew Cagney a écrit:
>Hmm,
>
>Using this trick:
>
>ac131313@nettle$ find | xargs grep remote-os9k.o
>Makefile.in:remote-os9k.o: remote-os9k.c $(defs_h) $(gdbcore_h) \
>config/i386/i386os9k.mt:TDEPFILES= i386-tdep.o remote-os9k.o
>ac131313@nettle$ grep i386os9k configure.tgt
>i[3456]86-*-os9k)       gdb_target=i386os9k ;;
>
>remote-array.c can be checked with --target=mips-elf.
>
>remote-os9k.c, remote-es.c and remote-st.c are each for obscure m68k systems (building m68k-elf won't check them and it can't break m68k GNU/Linux).
>
>Can I suggest also filing a bug report noteing the possability of dropping support for:
>m68*-ericsson-*)        gdb_target=es1800 ;;
>i[3456]86-*-os9k)       gdb_target=i386os9k ;;
>m68*-tandem-*)          gdb_target=st2000 ;;
>(I said they were obscure :-)
>
>So if mips-elf builds then yes, it can go on.

If I do a 
mkdir buildmips
cd buildmips
../src/configure --target=mips-linux-elf
make all-gdb
then 
remote-array.o is compiled without any warning.

I also checked the remote-os9k.o with
mkdir buildos9k
cd buildos9k
../src/configure --target=i386-unknown-os9k
mkdir gdb
cd gdb
../../src/gdb/configure --target=i386-unknown-os9k
  make

Here I get lots of errors in compilation
of remote-os9k.o 
but none seems to be related to my changes...


>Andrew

Thus I committed the whole as you stated.


Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


      reply	other threads:[~2002-04-29 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24  6:32 [RFA/RFC] printf (stderr,... ->fprintf_unfiltered (gdb_stderr,... in remote*.c Pierre Muller
2002-04-25  8:50 ` Andrew Cagney
2002-04-25  9:36   ` Pierre Muller
2002-04-25 10:17     ` Andrew Cagney
2002-04-26  1:56       ` [RFA 2nd] remote-*.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr, Pierre Muller
2002-04-26  6:12         ` Andrew Cagney
2002-04-29  4:02           ` Pierre Muller [this message]

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=4.2.0.58.20020429123751.00a75708@ics.u-strasbg.fr \
    --to=muller@cerbere.u-strasbg.fr \
    --cc=ac131313@cygnus.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