Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Brad Lucier <lucier@math.purdue.edu>,
	jsturm@one-point.com, atpoquet@ucdavis.edu, gcc@gcc.gnu.org,
	gdb-patches@sources.redhat.com
Subject: Re: Help needed with sparc
Date: Wed, 23 Jan 2002 18:27:00 -0000	[thread overview]
Message-ID: <3C4F6F76.FCA37E7D@redhat.com> (raw)
In-Reply-To: <or7kq8cwww.fsf@free.redhat.lsd.ic.unicamp.br>

Alexandre Oliva wrote:
> 
> On Jan 23, 2002, Brad Lucier <lucier@math.purdue.edu> wrote:
> 
> > Re:
> >> You must use a 64-bit gdb to debug 64-bit Solaris executables.
> 
> > Which version of gdb?  I got the following message when trying to
> > configure 5.1:
> 
> > env CC='cc -xildoff -xarch=v9' ./configure sparcv9-sun-solaris2.8
> > ...
> > checking for X... libraries /pkgs/XFree86-3.3.3.1/lib, headers /pkgs/XFree86-3.3.3.1/include
> > configure: error: *** Gdb does not support host sparcv9-sun-solaris2.8
> 
> gdb's configure recognizes sparc64-sun-solaris2.8, but not
> sparcv9-sun-solaris2.8.  Here's a patch that I've had for a while that
> addresses this inconsistency in GDB WRT other packages.  I'm not sure
> I've posted it before.  Ok to install?

Inconsistency WRT other packages?  The only configure script in which I
can
find the string "sparcv9" (and admitedly I've only searched the
developer
tools) is ld.

But I don't have a problem with it...


  parent reply	other threads:[~2002-01-24  2:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200201232315.g0NNFw309706@banach.math.purdue.edu>
2002-01-23 18:20 ` Alexandre Oliva
2002-01-23 18:26   ` Andrew Cagney
2002-01-23 18:48     ` Alexandre Oliva
2002-01-23 18:27   ` Michael Snyder [this message]
2002-01-23 18:39     ` Alexandre Oliva

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=3C4F6F76.FCA37E7D@redhat.com \
    --to=msnyder@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=atpoquet@ucdavis.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jsturm@one-point.com \
    --cc=lucier@math.purdue.edu \
    /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