From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: 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: Wed, 20 Mar 2013 18:29:00 -0000 [thread overview]
Message-ID: <201303201433.15976.vapier@gentoo.org> (raw)
In-Reply-To: <5149F70C.3040806@oarcorp.com>
[-- Attachment #1: Type: Text/Plain, Size: 1335 bytes --]
On Wednesday 20 March 2013 13:51:08 Joel Sherrill wrote:
> FYI you have to have bfin as installed to compile the simulator. I
> suppose this
> has never been noticed.
i'm guessing you're referring to the assembly of some fixed code file ? that
happens when timestamps get out of whack. i originally just wanted to add a
.h, but people requested i also add the source .s.
not sure if there's a way i could put this logic behind "if (file does not
exist) || (file is out of date && maintainer mode)" so it doesn't bite people
randomly ...
> Can I put a generic message for other targets that "dv-sockser hardware
> support is
> unavailable for your target" and let it go at that? Or do I specifically
> need to list the
> devices when dv-sockser.o is hard-coded in the Makefile.in?
since we don't have a large body of people clamoring for sim device support
under Windows, let's start with the simple version and avoid hardcoded lists.
> > and then add a TODO comment to each of these failing device modules with
> > something like "should change code to respect HAVE_DV_SOCKSER".
>
> What would such a message look like and where in the file would it go?
i was thinking of a /* TODO: ... */ in each device model file that
unconditionally uses dv-socker. e.g. sim/mips/dv-tx3904sio.c.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-20 18:29 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
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 [this message]
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=201303201433.15976.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.com \
--cc=ralf.corsepius@rtems.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