This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA 2nd] remote-*.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr,...


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]