From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Joel Sherrill <joel.sherrill@oarcorp.com>,
Ralf Corsepius <ralf.corsepius@rtems.org>,
Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"palves@redhat.com" <palves@redhat.com>,
"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>
Subject: Re: m32r sim was Re: one week to gdb-7.6 release?
Date: Thu, 04 Apr 2013 13:03:00 -0000 [thread overview]
Message-ID: <515D1D47.10301@rtems.org> (raw)
In-Reply-To: <20130329164237.GL4758@adacore.com>
On 03/29/2013 05:42 PM, Joel Brobecker wrote:
>>> Looking back at 7.5.91, I see that m32r unconditionally uses
>>> dv-sockser.o and
>>> I don't know how it built before.
> [...]
> Thank you again, guys, for being of top of it. Let's hope we are
> getting to the bottom of things...
FYI: My most recent built went without major problems on all platforms.
There are some minor issues (mostly with mingw32-w64), but I don't see a
pressing need to address them now.
> I have to admit that the number of iterations and the amount of
> research/testing needed in order to try to get this right is
> making me slightly nervous. Nothing we can do about it for
> this release. But for future releases, Ralf & Joel, do you think
> you could incorporate some regular testing of the HEAD on your
> end?
Well, I am not actually developing on gdb, but am packaging rtems-gdbs
for different host OSes. Therefore, I am usually jumping-in when gdb
releases a pre-release tarball and am testing building it. Apologies,
if this is inconvenient to you,
Ralf
next prev parent reply other threads:[~2013-04-04 6:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 16:09 Joel Brobecker
2013-03-20 16:14 ` Pedro Alves
2013-03-20 17:06 ` Jan Kratochvil
2013-03-20 17:08 ` Joel Sherrill
2013-03-20 17:20 ` Eli Zaretskii
2013-03-23 22:59 ` Eli Zaretskii
2013-03-24 0:01 ` Joel Brobecker
2013-03-24 0:07 ` Eli Zaretskii
2013-03-25 16:58 ` Joel Brobecker
2013-03-25 17:46 ` Eli Zaretskii
2013-03-25 18:10 ` Joel Brobecker
2013-03-29 8:02 ` Joel Brobecker
2013-03-29 14:03 ` Eli Zaretskii
2013-03-29 19:53 ` Joel Brobecker
2013-04-02 18:05 ` Eli Zaretskii
2013-04-05 13:03 ` Eli Zaretskii
2013-04-06 6:16 ` unbreak Windows hosted cross debugger builds (was: Re: one week to gdb-7.6 release?) Pedro Alves
2013-04-06 15:41 ` unbreak Windows hosted cross debugger builds " Eli Zaretskii
2013-03-29 15:23 ` one week to gdb-7.6 release? Ralf Corsepius
2013-03-29 16:42 ` m32r sim was " Joel Sherrill
2013-03-29 17:18 ` Mike Frysinger
2013-03-29 19:53 ` Joel Brobecker
2013-03-29 20:24 ` Joel Sherrill
2013-03-29 21:44 ` Joel Brobecker
2013-04-04 13:03 ` Ralf Corsepius [this message]
2013-04-10 15:01 ` Joel Brobecker
2013-03-25 19:08 ` Mark Kettenis
2013-03-25 19:12 ` Eli Zaretskii
2013-04-06 21:49 ` Pedro Alves
2013-04-07 3:58 ` Eli Zaretskii
2013-03-23 23:38 ` Joel Sherrill
2013-03-24 0:12 ` Mike Frysinger
2013-03-20 18:23 ` Ralf Corsepius
2013-04-01 19:56 ` 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=515D1D47.10301@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=joel.sherrill@oarcorp.com \
--cc=palves@redhat.com \
--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