Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Scott Bambrough <scottb@netwinder.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: changes to configure.in and configure
Date: Mon, 31 Jul 2000 09:58:00 -0000	[thread overview]
Message-ID: <3985AECC.DB7850E2@netwinder.org> (raw)
In-Reply-To: <20000731124035.N9027@cygnus.com>

I generated the patch on a NetWinder running ARM Linux, then ftp'd (text mode)
the file to a Windows box to mail it.  I suspect the Window's ftp program added
the \r's.

Scott

Chris Faylor wrote:
> 
> On Mon, Jul 31, 2000 at 12:25:00PM -0400, Scott Bambrough wrote:
> >I noticed last week that gdbserver was not building on my ARM Linux box
> >automatically even though it was specified in configdirs in
> >configure.tgt.  It seems none of the modifications to configdirs in
> >configure.tgt were being applied.  I'd like to apply the following
> >patch to configure.in which fixes this problem if no on has any
> >objections.  The changes to configure are the diffs after configure was
> >regenerated using autoconf 2.13 as Andrew suggested.
> 
> When I inspect your patch I see \r's at the end of every line.  Was it
> generated on a windows system?  Or is my mail reader screwed up?
> 
> cgf

-- 
Scott Bambrough - Software Engineer
REBEL.COM    http://www.rebel.com
NetWinder    http://www.netwinder.org
From tonic@sequent.com Mon Jul 31 10:59:00 2000
From: "Brethour, Tanya (tonic)" <tonic@sequent.com>
To: "'gdb-patches@sourceware.cygnus.com'" <gdb-patches@sourceware.cygnus.com>
Subject: notice_signals
Date: Mon, 31 Jul 2000 10:59:00 -0000
Message-id: <166E75C06F27D211B9860000C0AE13F509396354@wembley.sequent.com>
X-SW-Source: 2000-07/msg00378.html
Content-length: 288

Hello..

I was curious if anyone knew what the notice_signals function (ie.
hpux_thread_notice_signals, child_ops_to.notice_signals,
procfs_notice_signals) is trying to accomplish. Is this needed for ALL
platforms.. or what is the criteria to tell if it is needed?

Thanks so much,
Tanya
From curtisv@lineo.com Mon Jul 31 11:17:00 2000
From: Curtis Veit <curtisv@lineo.com>
To: gdb-patches@sources.redhat.com
Subject: Trouble compiling gdb for host=i686 target=mips
Date: Mon, 31 Jul 2000 11:17:00 -0000
Message-id: <3985C227.689537B8@lineo.com>
X-SW-Source: 2000-07/msg00379.html
Content-length: 3154

Hello,

I am going to be doing a bit of work in the near future with gdb (remote
debug for
various targets.  mips, ppc, sh, and arm) so I hope  in future I might
actually do
something helpful, for today though I'm afraid  that this is mainly a
request for help.
I've been trying to figure this out for a couple days now and find I am
lost!

I seem to be having trouble compiling gdb-5.0 configured for
--host=i686-pc-linux-gnu
and
--target=mipsel-elf-linux

I am running on an AMD K7 box.

I am using stock gdb-5.0 with the mips patches by Maciej W. Rozycki from

the gdb-patches mailing list.
(also available from  ' http://www.ds2.pg.gda.pl/~macro/gdb-5.0/ '.)

I am running OpenLinux 2.3 with some updates and gcc is version
egcs-2.91.66 19990314 (egcs-1.1.2 release)

My goal is to be able to remote debug an MIPS based development board
from IDT.
With both gdbserver and gdbstubs.

I did:
  ./configure --target=mipsel-elf-linux
  make

And got the following errors:

 gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I./../include
-I./../intl -I../intl -W -Wall -g -O2 -c stab-syms.c -o stab-syms.o
 echo timestamp > stab-syms.lo
 /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.
-D_GNU_SOURCE     -I. -I. -I./../include  -I./../intl -I../intl   -W
-Wall -g -O2 -c elf32-mips.c
 gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I./../include
-I./../intl -I../intl -W -Wall -g -O2 -c elf32-mips.c -o elf32-mips.o
 elf32-mips.c:1927: `BFD_RELOC_MIPS_HIGHER' undeclared here (not in a
function)
 elf32-mips.c:1927: initializer element for
`mips_reloc_map[21].bfd_reloc_val' is not constant
 elf32-mips.c:1928: `BFD_RELOC_MIPS_HIGHEST' undeclared here (not in a
function)
 elf32-mips.c:1928: initializer element for
`mips_reloc_map[22].bfd_reloc_val' is not constant
 make[3]: *** [elf32-mips.lo] Error 1
 make[3]: Leaving directory `/.ws/home/curtisv/gdb-5+/bfd'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/.ws/home/curtisv/gdb-5+/bfd'
 make[1]: *** [all-recursive-am] Error 2
 make[1]: Leaving directory `/.ws/home/curtisv/gdb-5+/bfd'
 make: *** [all-bfd] Error 2


I couldn't see anything wrong with the code in elf32-mips.c
(I guess I could have missed something here.)

Looking around for these declarations I find (in reloc.c)

 ENUM
   BFD_RELOC_MIPS_LITERAL
 ENUMDOC
   Relocation against a MIPS literal section.

 ENUM
   BFD_RELOC_MIPS_GOT16
 ENUMX
   BFD_RELOC_MIPS_CALL16
 ENUMEQX
   BFD_RELOC_MIPS_GPREL32
   BFD_RELOC_GPREL32
 ENUMX
   BFD_RELOC_MIPS_GOT_HI16
 ENUMX
   BFD_RELOC_MIPS_GOT_LO16
 ENUMX
   BFD_RELOC_MIPS_CALL_HI16
 ENUMX
   BFD_RELOC_MIPS_CALL_LO16
 ENUMX
   BFD_RELOC_MIPS_SUB
 ENUMX
   BFD_RELOC_MIPS_GOT_PAGE
 ENUMX
   BFD_RELOC_MIPS_GOT_OFST
 ENUMX
   BFD_RELOC_MIPS_GOT_DISP
 ENUMX
   BFD_RELOC_MIPS_HIGHER
 ENUMX
   BFD_RELOC_MIPS_HIGHEST
 COMMENT
 ENUMDOC

I have not yet figured out where ENUM, ENUMX, and friends are provided
or what they mean (although I can guess, I can't see the code) my greps
have
not provided any real insight. I'm feeling rather blind...

Does anyone know what is going on or where I should look?

Regards,
Curtis Veit
curtisv@lineo.com


       reply	other threads:[~2000-07-31  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3985A85C.C246C623@netwinder.org>
     [not found] ` <20000731124035.N9027@cygnus.com>
2000-07-31  9:58   ` Scott Bambrough [this message]
     [not found] ` <39863CD3.A527CEC3@cygnus.com>
2000-08-01  7:38   ` Scott Bambrough
     [not found]     ` <3986E6A3.6B3C@redhat.com>
2000-11-07 20:07       ` Andrew Cagney

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=3985AECC.DB7850E2@netwinder.org \
    --to=scottb@netwinder.org \
    --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