Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Rude, Randy [Cont]" <Randy.Rude@gdcanada.com>
To: 'Andrew Cagney' <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: RE: Problem building 5.2 for m68k-elf on Solaris
Date: Thu, 27 Jun 2002 10:48:00 -0000	[thread overview]
Message-ID: <83E3831A88E65844B01DB1A73FB66F9301684637@CSDNT99.cdcgy.com> (raw)

> > $ ../gdb-5.2/configure --target=m68k-elf
> >> [snip]
> >> 
> >> $ make
> >> [snip]
> >> gcc -c -g -O2  -I/usr/include/v9  -I. -I../../gdb-5.2/gdb
> >> -I../../gdb-5.2/gdb/config -DHAVE_CONFIG_H
> >> -I../../gdb-5.2/gdb/../include/opcode 
> >> -I../../gdb-5.2/gdb/../readline/..
> >> -I../bfd -I../../gdb-5.2/gdb/../bfd  -I../../gdb-5.2/gdb/../include
> >> -I../intl -I../../gdb-5.2/gdb/../intl  -DMI_OUT=1 -DUI_OUT=1 
> >> -Wimplicit
> >> -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses 
> >> -Wpointer-arith
> >> -Wuninitialized  ../../gdb-5.2/gdb/ser-unix.c
> >> In file included from /usr/include/netinet/in.h:41,
> >>                  from /usr/include/sys/socket.h:200,
> >>                  from ../../gdb-5.2/gdb/ser-unix.c:29:
> >> /usr/include/sys/stream.h:327: redefinition of `struct bcache'
> >> gmake[1]: *** [ser-unix.o] Error 1
> >> 
> >> Randy
> >> 
> > 
> > 
> > This is a namespace conflict.  The Solaris stream.h defines 
> struct bcache
> > which is also defined by GDB in bcache.h; the latter is 
> being included
> > unnecessarily in the files ser-unix.c, ser-pipe.c, and ser-tcp.c.
> > 
> > I was able to get the m68k-elf target to build by adding:
> > 
> > #define BCACHE_H 1
> > 
> > at the top of each of these files.  Not that I'd submit 
> that as a patch ;-)
> > but this allows me to build native Solaris and m68k-elf targets.
> > 
> > Hopefully someone more familiar with the code can come up 
> with a more
> > elegant solution?
> 
> Would you be able to determine/explain exactly how "bcache.h" 
> came to be 
> included?  Looking at ser-*.c, nothing obvious jumped out.
> 

bcache.h is:
        included from ../../work/gdb/symtab.h:31,
                 from ../../work/gdb/value.h:270,
                 from ../../work/gdb/gdbarch.h:41,
                 from ../../work/gdb/defs.h:1035,
                 from ../../work/gdb/ser-unix.c:22:

Hope that helps.

	Randy


             reply	other threads:[~2002-06-27 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 10:48 Rude, Randy [Cont] [this message]
2002-06-27 12:04 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-06-28  8:49 Rude, Randy [Cont]
2002-06-27 14:56 Rude, Randy [Cont]
2002-06-28 14:04 ` Andrew Cagney
2002-06-10 14:02 Rude, Randy [Cont]
2002-06-26 20:38 ` Andrew Cagney
2002-06-10 10:13 Rude, Randy [Cont]

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=83E3831A88E65844B01DB1A73FB66F9301684637@CSDNT99.cdcgy.com \
    --to=randy.rude@gdcanada.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@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