From: Mahesh Basavaraj Shavari <Mahesh.Shavari@kpitcummins.com>
To: <gdb@sourceware.org>
Subject: Mingw GDB build fails for M16C target
Date: Sat, 25 Apr 2009 13:57:00 -0000 [thread overview]
Message-ID: <82C3BC9106BCE149B63464D79D0A22FD0A68110C@sohm.kpit.com> (raw)
Hi,
I am trying to build a Mingw GDB for M16CM32C target using the
following source:
gdb-6.8.50.20090327
During make, I get the following error.
------------------------------------------------------------------------
-----------
mv version.c-tmp version.c
i386-pc-mingw32msvc-gcc -c -DHAVE_CONFIG_H -DPROFILE=1
-DWITH_PROFILE=-1 -DDEFAULT_INLINE=0 -Wall -DTIMER_A
-D__USE_MINGW_FSEEK -I.
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c -I../common
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../common
-I../../include
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../include
-I../../bfd
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../bfd
-I../../opcodes
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../opcodes
-I../../intl -g -O2 -D__USE_MINGW_ACCESS version.c
i386-pc-mingw32msvc-gcc -c -DHAVE_CONFIG_H -DPROFILE=1
-DWITH_PROFILE=-1 -DDEFAULT_INLINE=0 -Wall -DTIMER_A
-D__USE_MINGW_FSEEK -I.
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c -I../common
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../common
-I../../include
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../include
-I../../bfd
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../bfd
-I../../opcodes
-I/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/../../opcodes
-I../../intl -g -O2 -D__USE_MINGW_ACCESS
/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/gdb-if.c
/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/gdb-if.c: In
function `m32c_signal_to_host':
/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/gdb-if.c:541:
error: `SIGTRAP' undeclared (first use in this function)
/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/gdb-if.c:541:
error: (Each undeclared identifier is reported only once
/home/mahesh/GDB/gdb-6.8/gdb-6.8.50.20080811/sim/m32c/gdb-if.c:541:
error: for each function it appears in.)
make[3]: *** [gdb-if.o] Error 1
make[3]: Leaving directory
`/home/mahesh/GDB/gdb-6.8/build/m32c-elfbld6.8.50.20080811/sim/m32c'
make[2]: *** [all] Error 1
make[2]: Leaving directory
`/home/mahesh/GDB/gdb-6.8/build/m32c-elfbld6.8.50.20080811/sim'
make[1]: *** [all-sim] Error 2
make[1]: Leaving directory
`/home/mahesh/GDB/gdb-6.8/build/m32c-elfbld6.8.50.20080811'
make: *** [all] Error 2
------------------------------------------------------------------------
-----------
M16C target GNU Linux toolchain was built using the following sources.
Gcc-4.3.3
Binutils-2.19
Newlib-1.16.0
The native mingw toolchain (i386-pc-mingw32msvc-gcc) for i386 was built
using the following source.
Gcc version 3.4.5
Any help would be highly appreciated.
Thanking you in anticipation.
Regards,
Mahesh Shavari.
------------------------------------------------------------------------
-----------
next reply other threads:[~2009-04-25 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 13:57 Mahesh Basavaraj Shavari [this message]
2009-04-29 6:13 ` Kevin Buettner
2009-04-29 8:40 Mahesh Basavaraj Shavari
2009-08-05 12:59 Mahesh Basavaraj Shavari
2009-08-14 4:24 ` DJ Delorie
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=82C3BC9106BCE149B63464D79D0A22FD0A68110C@sohm.kpit.com \
--to=mahesh.shavari@kpitcummins.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