Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>,
	Joel Brobecker <brobecker@adacore.com>,
	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: Fri, 29 Mar 2013 17:18:00 -0000	[thread overview]
Message-ID: <201303291230.37045.vapier@gentoo.org> (raw)
In-Reply-To: <5155A93E.3050509@oarcorp.com>

[-- Attachment #1: Type: Text/Plain, Size: 1863 bytes --]

On Friday 29 March 2013 10:46:22 Joel Sherrill wrote:
> On 3/29/2013 1:54 AM, Ralf Corsepius wrote:
> > 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?
> 
> Looking back at 7.5.91, I see that m32r unconditionally uses
> dv-sockser.o and
> I don't know how it built before.

two reasons:
 - it never defined HAVE_DV_SOCKSER
 - it adds dv-sockser.o in Makefile.in only to then clear the variable
so it had all the framework for the code, but never actually enabled it :).  
your patch actually fixed that part.

> The references to dv-sockser.o methods appear to be properly
> conditionalized in the code.  So it is the Makefile.in and our
> interpretation that the simulated
> hardware should be "always on" versus "yes enabled" by default.
> 
> Attached is an untested patch.

you should also update m32r/tconfig.in and remove the 3 lines related to #if 
0/HAVE_DV_SOCKSER.

also, you'll need to apply the same fix to frv.  it too has proper 
HAVE_DV_SOCKSER conditionals, and explicitly lists it in Makefile.in, only to 
later disable it.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-29 16:26 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 [this message]
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

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=201303291230.37045.vapier@gentoo.org \
    --to=vapier@gentoo.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=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