From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: mipxtx39 sim build failure
Date: Thu, 10 Nov 2016 21:53:00 -0000 [thread overview]
Message-ID: <f44de318-3a53-6370-2502-14d9c8a326ce@oarcorp.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8"; format=flowed, Size: 3174 bytes --]
Hi
I was updating the baseline RTEMS gdb configuration to
7.12 from 7.11 and noticed that our mipstx39 build
(just used for the tx39 simulator) was still at 7.9. I bumped
it to 7.12 and got the following build errors:
/usr/bin/gcc -O2 -pipe -I/data/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/tmp/sb-joel/4.12/rtems-mips/home/joel/rtems-4.11-work/tools/4.12/include -DHAVE_CONFIG_H -DWITH_ALIGNMENT=NONSTRICT_ALIGNMENT -DWITH_TARGET_WORD_BITSIZE=32 -DWITH_TARGET_WORD_MSB=31 -DWITH_DEFAULT_TARGET_BYTE_ORDER=BFD_ENDIAN_BIG -DWITH_FLOATING_POINT=HARD_FLOATING_POINT -DWITH_TARGET_FLOATING_POINT_BITSIZE=32 -DWITH_HW=1 -DDEFAULT_INLINE=0 -DWITH_RESERVED_BITS=1 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement -Wempty-body -Wmissing-parameter-type -Wold-style-declaration -Wold-style-definition -Wformat-nonliteral -DSUBTARGET_R3900=1 -DMIPS_MACH_DEFAULT=bfd_mach_mips8000 -I. -I../../../gdb-7.12/sim/mips -I../common -I../../../gdb-7.12/sim/mips/../common -I../../include -I../../../gdb-7.12/sim/mips/../..//include -I../../bfd -I../../../gdb-7.12/sim/mips/../..//bfd -I../../opcodes -I../../../gdb-7.12/sim/mips/../..//opcodes -g -O2 -c -o dv-tx3904cpu.o -MT dv-tx3904cpu.o -MMD -MP -MF .deps/dv-tx3904cpu.Tpo ../../../gdb-7.12/sim/mips/dv-tx3904cpu.c
In file included from ../../../gdb-7.12/sim/mips/dv-tx3904cpu.c:22:0:
../../../gdb-7.12/sim/mips/dv-tx3904cpu.c: In function âdeliver_tx3904cpu_interruptâ:
../../../gdb-7.12/sim/mips/sim-main.h:679:64: error: âSDâ undeclared (first use in this function)
#define SignalExceptionNMIReset() signal_exception (SD, CPU, cia, NMIReset)
^
../../../gdb-7.12/sim/mips/dv-tx3904cpu.c:150:7: note: in expansion of macro âSignalExceptionNMIResetâ
SignalExceptionNMIReset();
^
../../../gdb-7.12/sim/mips/sim-main.h:679:64: note: each undeclared identifier is reported only once for each function it appears in
#define SignalExceptionNMIReset() signal_exception (SD, CPU, cia, NMIReset)
^
../../../gdb-7.12/sim/mips/dv-tx3904cpu.c:150:7: note: in expansion of macro âSignalExceptionNMIResetâ
SignalExceptionNMIReset();
^
../../../gdb-7.12/sim/mips/sim-main.h:679:68: error: âCPUâ undeclared (first use in this function)
#define SignalExceptionNMIReset() signal_exception (SD, CPU, cia, NMIReset)
^
../../../gdb-7.12/sim/mips/dv-tx3904cpu.c:150:7: note: in expansion of macro âSignalExceptionNMIResetâ
SignalExceptionNMIReset();
^
Does anyone have suggestions?
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35806
Support Available (256) 722-9985
\x16º&ÖëzÛ«xÛb²Ö«r\x18\x1d
next reply other threads:[~2016-11-10 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 21:53 Joel Sherrill [this message]
2016-11-11 6:37 ` Mike Frysinger
2016-11-11 15:48 ` Joel Sherrill
[not found] ` <20161111193219.GJ21655@vapier.lan>
2016-11-11 20:48 ` Joel Sherrill
2016-11-12 4:40 ` Mike Frysinger
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=f44de318-3a53-6370-2502-14d9c8a326ce@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
/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