Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: "Ratin Rahman (mratin)" <mratin@cisco.com>
Cc: linux-mips@linux-mips.org
Subject: Re: gdbserver
Date: Thu, 28 Jun 2007 14:41:25 -0700	[thread overview]
Message-ID: <46842B05.5050103@avtrex.com> (raw)
In-Reply-To: <27801B4D04E7CA45825B0E0CE60FE10A0410F0D6@xmb-sjc-237.amer.cisco.com>

Ratin Rahman (mratin) wrote:
> Anybody had luck with compiling gdbserver for mipsel? I am using x86
> based machine running Fedora 2.6.11 kernel, the target device is IDT 434
> running Mipsel 2.6.10 kernel. The gcc crosscompiler is mipsel-linux-gcc
> and version 3.2.3.
> 
> I did a ./configure --host=mipsel-linux-gnu --target=mipsel-linux-gnu
> followed by a make. Make failed with the messages: 
> 
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h:33: syntax error
> before numeric constant
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h:49: syntax error
> before numeric constant
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h:61: syntax error
> before numeric constant
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h:94: syntax error
> before numeric constant
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h:112: syntax error
> before numeric constant
> linux-low.c: In function `kill_lwp':
> linux-low.c:760: warning: unused variable `tkill_failed'
> make: *** [linux-low.o] Error 1
> [root@Clearnet gdbserver]# nano
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h
> [root@Clearnet gdbserver]# nano
> /opt/mipseltools/mipsel-linux/sys-include/sys/ptrace.h
> 
> 
> The content of ptrace.h has the enums declared as 
> 
> /* Type of the REQUEST argument to `ptrace.'  */
> enum __ptrace_request
> {
>   /* Indicate that the process making this request should be traced.
>      All signals received by this process can be intercepted by its
>      parent, and its parent can use the other `ptrace' requests.  */
>   PTRACE_TRACEME = 0,
> <==================================line 33
> #define PT_TRACE_ME PTRACE_TRACEME
> 
>   /* Return the word in the process's text space at address ADDR.  */
>   PTRACE_PEEKTEXT = 1,
> #define PT_READ_I PTRACE_PEEKTEXT
> 
> 
> ..which looks pretty normal to me , anybod yhave any clue? 
> Thanks,
> 

Perhaps your toolchain is broken, or perhaps you need to configure 
differently.

With my glibc-2.3.3/gcc-3.4.3 toolchain I do:
../gdb-6.6/configure  --target=mipsel-linux --host=mipsel-linux 
--build=i686-pc-linux-gnu

Then make and voila! gdb, gdbserver et al. are built.

David Danay

  parent reply	other threads:[~2007-06-28 21:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 16:14 [PATCH] generic clk API implementation for MIPS Atsushi Nemoto
2007-06-26  9:37 ` Franck Bui-Huu
2007-06-26 14:33   ` Atsushi Nemoto
2007-06-26 15:20     ` Franck Bui-Huu
2007-06-26 16:33       ` Atsushi Nemoto
2007-06-26 20:02         ` Franck Bui-Huu
2007-06-27  7:51           ` Atsushi Nemoto
2007-06-27 15:39         ` Christoph Hellwig
2007-06-28  2:22           ` Atsushi Nemoto
2007-06-28  8:37             ` Christoph Hellwig
2007-06-28  9:26               ` Atsushi Nemoto
2007-06-28 20:45               ` gdbserver Ratin Rahman (mratin)
2007-06-28 20:45                 ` gdbserver Ratin Rahman (mratin)
2007-06-28 21:41                 ` David Daney [this message]
2007-06-28 22:19                   ` gdbserver Ratin Rahman (mratin)
2007-06-28 22:19                     ` gdbserver Ratin Rahman (mratin)
2007-06-29  1:26                   ` upgrading glibc for mipsel Ratin Rahman (mratin)
2007-06-29  1:26                     ` Ratin Rahman (mratin)
2007-06-29  2:03                     ` David Daney
2007-06-29  2:26                       ` Jason Talley
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12 19:22 gdbserver Lanny DeVaney
2002-03-12 20:45 ` gdbserver Johannes Stezenbach
2002-03-12 21:46   ` gdbserver Lanny DeVaney
2002-03-12 22:10 ` gdbserver Daniel Jacobowitz
2002-03-12 22:16   ` gdbserver Lanny DeVaney

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=46842B05.5050103@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mratin@cisco.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