From: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
To: aoliva@redhat.com (Alexandre Oliva)
Cc: gdb@sources.redhat.com
Subject: Re: GDB CVS won't build on Solaris/x86
Date: Thu, 14 Feb 2002 00:18:00 -0000 [thread overview]
Message-ID: <200202140818.JAA11274@reaktor.regent.e-technik.tu-muenchen.de> (raw)
In-Reply-To: <or7kq0e344.fsf@free.redhat.lsd.ic.unicamp.br>; from "Alexandre Oliva" at Jan 30, 102 9:01 am
Should be fixed now, with the recent changes to i386v4-nat.c and:
2002-02-14 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
* config/i386/i386sol2.mh (NATDEPFILES): Add i387-nat.o, needed by
i386v4-nat.o now. Add gcore.o, Solaris x86 supports gcore.
--- ./config/i386/i386sol2.mh.orig Fri Jan 18 05:50:59 2002
+++ ./config/i386/i386sol2.mh Sat Feb 2 11:36:22 2002
@@ -4,5 +4,5 @@ XM_FILE= xm-i386v4.h
XM_CLIBS= -lsocket -lnsl
NAT_FILE= nm-i386sol2.h
-NATDEPFILES= core-regset.o fork-child.o i386v4-nat.o corelow.o procfs.o \
- proc-api.o proc-events.o proc-flags.o proc-why.o
+NATDEPFILES= core-regset.o fork-child.o i386v4-nat.o i387-nat.o corelow.o \
+ procfs.o proc-api.o proc-events.o proc-flags.o proc-why.o gcore.o
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c: In function `supply_fpregset':
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:184: `LAST_FPU_CTRL_REGNUM' undeclared (first use in this function)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:184: (Each undeclared identifier is reported only once
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:184: for each function it appears in.)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:190: `FCS_REGNUM' undeclared (first use in this function)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:196: `FOP_REGNUM' undeclared (first use in this function)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c: In function `fill_fpregset':
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:219: `LAST_FPU_CTRL_REGNUM' undeclared (first use in this function)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:228: `FCS_REGNUM' undeclared (first use in this function)
> /home/phd/oliva/src/tool/egcs/gdb/i386v4-nat.c:235: `FOP_REGNUM' undeclared (first use in this function)
> make[2]: *** [i386v4-nat.o] Error 1
>
> It's been like that for the past few weeks, but I still haven't had a
> chance to investigate, so I wouldn't mind if someone beat me to it :-)
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist *Please* write to mailing lists, not to me
>
>
--
Peter Schauer pes@regent.e-technik.tu-muenchen.de
next prev parent reply other threads:[~2002-02-14 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 22:59 Alexandre Oliva
2002-01-30 0:12 ` Peter.Schauer
2002-01-30 14:43 ` Mark Kettenis
2002-02-14 0:18 ` Peter.Schauer [this message]
2002-03-06 13:17 ` 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=200202140818.JAA11274@reaktor.regent.e-technik.tu-muenchen.de \
--to=peter.schauer@regent.e-technik.tu-muenchen.de \
--cc=aoliva@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