All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: "Griffin, Aubrey, BMCIO" <aubreygriffin@att.com>
Cc: 'Parisc-linux Mailing List' <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Problem compiling GDB
Date: Mon, 19 Nov 2001 18:46:38 +0000	[thread overview]
Message-ID: <20011119184638.B11431@linuxcare.com> (raw)
In-Reply-To: <5360C45FAB301541AEB3C6A45A6B6A0270684F@ocst09.ugd.att.com>; from aubreygriffin@att.com on Mon, Nov 12, 2001 at 05:16:37PM -0500

PT_CR30 used to exist in offset.h, see

http://cvs.parisc-linux.org/linux/include/asm-parisc/ptrace.h.diff?r1=1.12&r2=1.13

I just checked out the latest gdb source from cvs.parisc-linux.org and
changed PT_CR30 in gdb/pa-linux-nat.c to '-1'.  Builds now.  the gdbserver
stuff wouldn't build anyway, as it tries to include offsets.h, not offset.h.

btw, there is a gdb .deb on http://ftp.parisc-linux.org/unofficial-debs

Richard


On Mon, Nov 12, 2001 at 05:16:37PM -0500, Griffin, Aubrey, BMCIO wrote:
> All,
> 
> I am trying to compile GDB.
> 
> I downloaded gdb-20011024 from http://ftp.parisc-linux.org/cvs/
> 
> The compilation of gdb failed. There is an undefined constant PT_CR30. This
> is used in
> gdb/pa-linux-nat.c and gdb/gdb/gdbserver/low-linux.c.
> 
> Some PT_ constants are defined in /usr/include/asm/offset.h, but not
> PT_CR30.
> 
> Should this gdb bundle compile?
> 
> Is there another gdb package that compiles on this platform?
> 
> All help is appreciated.
> 
> Thanks in advance,
> Aubrey Griffin
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> 

      reply	other threads:[~2001-11-19 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 22:16 [parisc-linux] Problem compiling GDB Griffin, Aubrey, BMCIO
2001-11-19 18:46 ` Richard Hirst [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=20011119184638.B11431@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=aubreygriffin@att.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.