Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Christian Joensson <christian@j-son.org>
Cc: "Tom 'spot' Callaway" <tcallawa@redhat.com>,
	gdb-gnats@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: build/955: build failure with GDB-5.3: sparc-nat.c structure redefinition errors with sparc64-linux, glibc-2.2.x
Date: Wed, 08 Oct 2003 09:03:00 -0000	[thread overview]
Message-ID: <87smm4gkzi.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20031008094017.A28615@u1sparc.j-son.org> (Christian Joensson's message of "Wed, 8 Oct 2003 09:40:17 +0200")

On Wed, 8 Oct 2003, Christian Joensson stipulated:
> On Wed, Oct 08, 2003 at 08:29:05AM +0100, Nix wrote:
>> On Mon, 25 Aug 2003, Christian Joensson uttered the following:
>> > uhm, just tried gdb cvs HEAD, as of Sun Aug 24 12:01:38 UTC 2003, same thing:
>> 
>> I'm back, at last.
>> 
>> > In file included from /usr/include/asm/reg.h:7,
>> >                  from /home/chj/src/gdb/sparc-nat.c:38:
>> > /usr/include/asm-sparc64/reg.h:49: error: redefinition of `struct fpu'
>> 
>> sparc64? Are you trying to build a 64-bit gdb?
> 
> uhm, yes, to debug 64-bit binaries....

Oh, OK, so a lot of my suppositions are incorrect.

> uhm, a 64-bit gdb is not that easy to accomplish, I guess, but
> there'll be one in a future Aurora SPARC Linux, a development
> gdb64-5.2-ish src rpm is available:

sparc-nat.c hasn't changed much since 5.3 (although it's changing like
billyo on the SPARC branch of course). You could always grab the
gdb64-5.2 and see what's been done to sparc-nat.c in there, but it makes
more sense to try to forward-port the whole lot (diffing against
gdb-5.2-release, I guess, or see if the author posted a patch anywhere).

Of course doing this is a bit pointless if the author of that patch is
forward-porting it right now or kept it in synch with GDB CVS, which is
not beyond the bounds of possibility.

> ftp://auroralinux.org/pub/aurora/scratch

Snarfing gdb64, this could be interesting :)

-- 
`If you want a vision of the future, it is a wireless broadband network
 feeding requests for foreign money-laundering assistance into a human
 temporal lobe, forever. With banner ads.' --- John M. Ford


  reply	other threads:[~2003-10-08  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030427150800.19859.qmail@sources.redhat.com>
2003-04-27 20:45 ` Daniel Jacobowitz
2003-04-27 22:03   ` c.christian.joensson
2003-05-10  7:57   ` Christian Joensson
2003-05-10 13:35     ` Christian Joensson
2003-05-10 21:30       ` Nix
2003-08-25  6:57       ` Christian Joensson
2003-10-08  7:29         ` Nix
2003-10-08  7:40           ` Christian Joensson
2003-10-08  9:03             ` Nix [this message]
2003-10-09  0:47             ` Michael Snyder

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=87smm4gkzi.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=christian@j-son.org \
    --cc=gdb-gnats@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tcallawa@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