From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Ralf Corsepius <ralf.corsepius@rtems.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [gdb-7.5.91] mips sim fails to build on mingw32
Date: Sun, 17 Mar 2013 16:11:00 -0000 [thread overview]
Message-ID: <5145EB0E.4040104@oarcorp.com> (raw)
In-Reply-To: <20130317160230.GN4474@adacore.com>
On 3/17/2013 11:02 AM, Joel Brobecker wrote:
>> 2013-03-16 Joel Sherrill <joel.sherrill@oarcorp.com>
>>
>> * configure.ac: Avoid use of dv-sockser on *mingw32*
>> * aclocal.m4: Regenerated.
>> * configure: Regenerated.
> [...]
>> +
>> SIM_AC_OPTION_HARDWARE($hw_enabled,$hw_devices,$hw_extra_devices)
>> -mips_extra_objs="dv-sockser.o"
>> -AC_SUBST(mips_extra_objs)
>> +
>> +mips_extra_objs=
>> +dnl make sure the dv-sockser code can be supported (i.e. windows)
>> +case ${host} in
>> + *mingw32*) ;;
> I would change that to *mingw*. We might get mingw64 someday...
:) The patch I posted simultaneously to address this in common/acinclude.m4
also has mingw32. I will fix it. But that patch needs more review.
cd sim
grep dv-sockser.o */Makefile.in
grep dv-sockser.o */configure.ac
And you will see what I need advice on. The patch in the next email
fixes bfin and mips I think. Scratches problem on other targets.
>
>> + *)
>> + AC_DEFINE_UNQUOTED([HAVE_DV_SOCKSER], 1, [Define if dv-sockser is usable.])
>> + mips_extra_objs="${mips_extra_objs} dv-sockser.o"
>> + ;;
>> +esac
>> +
>> +AC_SUBST([mips_extra_objs], ${mips_extra_objs})
>> +
>> +## mips_extra_objs="dv-sockser.o"
>> +## AC_SUBST(mips_extra_objs)
> Can you also remove the commented-out code?
>
The mips/configure.ac in the new patch relies on common/acinclude.m4 to
tell it whether or to use dv-sockser.o. This centralizes the test for
which hosts
it supports.
--
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 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2013-03-17 16:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 18:38 Joel Sherrill
[not found] ` <5143F627.3030905@rtems.org>
2013-03-16 6:56 ` Ralf Corsepius
2013-03-16 15:08 ` Joel Sherrill
2013-03-16 18:11 ` Joel Brobecker
2013-03-16 18:48 ` Joel Sherrill
2013-03-16 23:24 ` Mike Frysinger
2013-03-17 1:03 ` Joel Brobecker
2013-03-17 15:10 ` Mike Frysinger
2013-03-17 1:13 ` Joel Sherrill
2013-03-17 15:09 ` Mike Frysinger
2013-03-17 16:02 ` Joel Brobecker
2013-03-17 16:11 ` Joel Sherrill [this message]
2013-03-17 4:16 ` Ralf Corsepius
2013-03-17 16:05 ` Joel Sherrill
[not found] ` <201303181405.55098.vapier@gentoo.org>
2013-03-20 17:51 ` Joel Sherrill
2013-03-20 18:29 ` Mike Frysinger
2013-03-20 18:48 ` Joel Sherrill
2013-03-27 11:21 ` Pedro Alves
2013-03-27 17:00 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 23:17 GDB 7.5.91 available for testing Joel Brobecker
[not found] ` <5140894E.6000308@oarcorp.com>
2013-03-15 12:52 ` [gdb-7.5.91] mips sim fails to build on mingw32 Ralf Corsepius
2013-03-15 18:13 ` Mike Frysinger
2013-03-15 18:32 ` Ralf Corsepius
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=5145EB0E.4040104@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ralf.corsepius@rtems.org \
--cc=vapier@gentoo.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