From: "Hans Kester" <kester.hans@gmail.com>
To: insight@sourceware.org
Subject: MinGW build failure for mips-elf
Date: Wed, 09 Apr 2008 08:30:00 -0000 [thread overview]
Message-ID: <93da74750804090130v26b381d0x7a96018dddc3500b@mail.gmail.com> (raw)
When building Insight 6.8 on MinGW/MSYS for a mips-elf target you get
the follwing error:
../../../../insight-6.8/sim/mips/../common/sim-signal.c: In function
`sim_signal_to_host':
../../../../insight-6.8/sim/mips/../common/sim-signal.c:60: error:
`SIGTRAP' undeclared (first use in this function)
../../../../insight-6.8/sim/mips/../common/sim-signal.c:60: error:
(Each undeclared identifier is reported only once
../../../../insight-6.8/sim/mips/../common/sim-signal.c:60: error: for
each function it appears in.)
make[3]: *** [sim-signal.o] Error 1
make[3]: Leaving directory `/gcc/build-mips-elf/insight/sim/mips'
make[2]: *** [all] Error 1
make[2]: Leaving directory `/gcc/build-mips-elf/insight/sim'
make[1]: *** [all-sim] Error 2
make[1]: Leaving directory `/gcc/build-mips-elf/insight'
make: *** [all] Error 2
This can be fixed by patching sim/common/sim-signal.c @ 29:
- #ifdef _MSC_VER
+ #ifdef _WIN32
I don't know if that breaks builds on other hosts, but it works for MinGW.
Could someone patch this at the right places?
Regards,
Hans Kester
next reply other threads:[~2008-04-09 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 8:30 Hans Kester [this message]
2008-04-09 17:38 ` Keith Seitz
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=93da74750804090130v26b381d0x7a96018dddc3500b@mail.gmail.com \
--to=kester.hans@gmail.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).