Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nix <nix@esperi.demon.co.uk>
To: Christian Joensson <c.christian.joensson@telia.com>
Cc: 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: Sat, 10 May 2003 21:30:00 -0000	[thread overview]
Message-ID: <87k7cy5x3l.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20030510153527.A5854@u1sparc.j-son.org>

On Sat, 10 May 2003, Christian Joensson muttered drunkenly:
> On Sat, May 10, 2003 at 09:57:12AM +0200, Christian Joensson wrote:
>> On Sun, Apr 27, 2003 at 11:33:21AM -0400, Daniel Jacobowitz wrote:
>> > On Sun, Apr 27, 2003 at 03:08:00PM -0000, Nix wrote:
>> > > The following reply was made to PR build/955; it has been noted by GNATS.
>> > > 
>> > > From: Nix <nix@esperi.demon.co.uk>
>> > > To: Christian =?iso-8859-1?q?J=F6nsson?= <c.christian.joensson@telia.com>
>> > > Cc: <nobody@sources.redhat.com>, <gdb-gnats@sources.redhat.com>,
>> > >    <gdb-prs@sources.redhat.com>, <aurora-sparc-devel@linuxpower.org>
>> > > Subject: Re: build/955: build failure with GDB-5.3: sparc-nat.c structure redefinition errors with sparc64-linux, glibc-2.2.x
>> > > Date: 27 Apr 2003 15:45:01 +0100
>> > > 
>> > >  On Sun, 27 Apr 2003, Christian Jönsson spake:
>> > >  > http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&databas
>> > >  > e=gdb&pr=955
>> > >  > 
>> > >  > Is *anything* happening on this issue in gdb cvs HEAD?
>> > >  
>> > >  My apologies for not following up; this patch, abstracted from Debian
>> > >  (where fading memory tells me it is due to Daniel Jacobowitz), fixes it,
>> > >  but is probably too ugly to go in; the incompatibility test should
>> > >  really be done by configure:
>> > 
>> > Right on the origin and ugliness counts, which is why I never got
>> > around to doing anything about it.  But it's better than nothing, since
>> > it lets sparc-linux build, so I suppose it should go in... does anyone object?
>> >   
>> > >  Index: gdb/gdb/sparc-nat.c
>> > >  ===================================================================
>> > >  RCS file: /cvs/src/src/gdb/sparc-nat.c,v
>> > >  retrieving revision 1.13.12.1
>> > >  diff -u -r1.13.12.1 sparc-nat.c
>> > >  --- gdb/gdb/sparc-nat.c	3 Dec 2002 22:35:49 -0000	1.13.12.1
>> > >  +++ gdb/gdb/sparc-nat.c	27 Apr 2003 14:39:53 -0000
>> > >  @@ -33,6 +33,13 @@
>> > >   #include <sys/ptrace.h>
>> > >   #include <sys/wait.h>
>> > >   #ifdef __linux__
>> > >  +/* Sadly, <sys/ucontext.h> conflicts with <asm/reg.h> on Linux.  And
>> > >  +   -D_GNU_SOURCE brings in <sys/ucontext.h> implicitly with <signal.h>.
>> > >  +   Hack around this.  */
>> > >  +#undef FPU_REGS_TYPE
>> > >  +#define fpu asm_reg_fpu
>> > >  +#define fq asm_reg_fq
>> > >  +#define fpq asm_reg_fpq
>> > >   #include <asm/reg.h>
>> > >   #else
>> > >   #include <machine/reg.h>
>> > >  
>> > >  
>> > >  -- 
>> > >  `It is an unfortunate coincidence that the date locarchive.h was
>> > >   written (in hex) matches Ritchie's birthday (in octal).'
>> > >                 -- Roland McGrath on the libc-alpha list
>> > > 
>> > 
>> > -- 
>> > Daniel Jacobowitz
>> > MontaVista Software                         Debian GNU/Linux Developer
>> 
>> ping... how's it going?
>> 
> 
> I just thougt I'd test your suggested patch... it still fails...
> 
> This is how the compile stops with error in the current gdb cvs HEAD:
> 
> gcc -c -g -O2    -I. -I/home/chj/src/gdb -I/home/chj/src/gdb/config -DLOCALEDIR="\"/usr/local/gcc-binutils/share/locale\"" -DHAVE_CONFIG_H -I/home/chj/src/gdb/../include/opcode -I/home/chj/src/gdb/../readline/.. -I../bfd -I/home/chj/src/gdb/../bfd  -I/home/chj/src/gdb/../include -I../intl -I/home/chj/src/gdb/../intl  -DMI_OUT=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized  /home/chj/src/gdb/sparc-nat.c
> In file included from /usr/include/asm/reg.h:4,
>                  from /home/chj/src/gdb/sparc-nat.c:36:
> /usr/include/asm-sparc64/reg.h:49: error: redefinition of `struct fpu'
> /home/chj/src/gdb/sparc-nat.c: In function `fetch_inferior_registers':
> /home/chj/src/gdb/sparc-nat.c:99: warning: cast from pointer to integer of different size
> /home/chj/src/gdb/sparc-nat.c:103: warning: implicit declaration of function `memcpy'

Oh. How strange, it workedforme.

I'll see if I can reproduce & fix it tomorrow (assuming Daniel doesn't
get to it before that).

-- 
`It is an unfortunate coincidence that the date locarchive.h was
 written (in hex) matches Ritchie's birthday (in octal).'
               -- Roland McGrath on the libc-alpha list


  reply	other threads:[~2003-05-10 21:30 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 [this message]
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
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=87k7cy5x3l.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.demon.co.uk \
    --cc=c.christian.joensson@telia.com \
    --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