From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, palves@redhat.com,
jan.kratochvil@redhat.com, ralf.corsepius@rtems.org,
vapier@gentoo.org, joel.sherrill@oarcorp.com
Subject: Re: one week to gdb-7.6 release?
Date: Fri, 29 Mar 2013 15:23:00 -0000 [thread overview]
Message-ID: <51553AA8.8020705@rtems.org> (raw)
In-Reply-To: <20130329015924.GA14360@adacore.com>
On 03/29/2013 02:59 AM, Joel Brobecker wrote:
> I was wondering if this discussion was stalled, or if it was just
> a matter of not finding the time to do the implementation.
Sorry, in my case, it's simply lack of time.
> I could
> possibly take care of it tomorrow if you'd like. There is not real
> rush, however, as I will be off next week, and thus unable to create
> a release at least until Tue Apr 9th.
I just did a test-rebuild with current gdb-7_6-branch (presuming Joel's
new patches are in).
Using the same set of configuration options, I have been using for
gdb-7.5.x, all targets build fine on Linux.
However, there is a new breakdown for the m32r on mingw32-w64-{x86_64,i386}:
..../configure --build=i386-pc-linux-gnu \
--host=x86_64-w64-mingw32 --target=m32r-rtems4.11
--enable-sim [...] \
...
checking how to recognize dependent libraries... configure: error:
Sorry, but hardware support in this simulator unconditionally
relies on dv-sockser.o which is unavailable for your host. Please fix
this simulator.
...
As gdb-7.5.x built fine with the same configuration, this to me
qualifies as a regression - Or is this just a latent, so far silently
accepted, but dysfunctional part being revealed by the new configuration
magic?
Ralf
next prev parent reply other threads:[~2013-03-29 7:35 UTC|newest]
Thread overview: 36+ 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 ` Ralf Corsepius [this message]
2013-03-29 16:42 ` m32r sim was Re: one week to gdb-7.6 release? 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
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
2013-03-29 12:53 Joel Sherrill
2013-03-29 14:15 ` Eli Zaretskii
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=51553AA8.8020705@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