From: Joern Rennecke <joern.rennecke@embecosm.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Implement gdbarch_gdb_signal_{to,from}_target
Date: Mon, 12 Aug 2013 08:48:00 -0000 [thread overview]
Message-ID: <20130812044819.f4bsof7l448gs4cw-nzlynne@webmail.spamcop.net> (raw)
In-Reply-To: <m3a9kny3b6.fsf@redhat.com>
Quoting Sergio Durigan Junior <sergiodj@redhat.com>:
> Sorry, but how are you building this? I'm having trouble reproducing
> the failure. I suppose you're building a GDB for AVR only,
yes, using --target=avr for configure.
> which is
> probably not building linux-tdep.o, where both
> linux_gdb_signal_{to,from}_target functions are defined.
Indeed, avr-tdep.o is the only *tdep* file built.
> There is no avr-linux-tdep.c, which means that when we're not building
> for a Linux target such functions won't be available because
> linux-tdep.o won't be built. I'm not sure how to solve this specific
> problem (whether to propose this avr-linux-tdep or to solve this with
> #ifdef's). Opinions are welcome.
Is linux-tdep.c really the right place for the host specific support
functions?
> For now, I have chosen to revert the patch for AVR. This is not an
> urgent thing, and IMO it's more important to keep the tree buildable.
> Meanwhile we can discuss alternatives.
>
> I checked-in the following patch.
>
> http://sourceware.org/ml/gdb-cvs/2013-08/msg00050.html
Yes, avr-gdb is building again for now.
next prev parent reply other threads:[~2013-08-12 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 1:49 Joern Rennecke
2013-08-12 3:51 ` Sergio Durigan Junior
2013-08-12 8:48 ` Joern Rennecke [this message]
2013-08-12 11:07 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2013-07-26 20:13 Sergio Durigan Junior
2013-07-27 17:57 ` Doug Evans
2013-08-07 20:54 ` Sergio Durigan Junior
2013-07-29 16:43 ` Pedro Alves
2013-08-09 16:56 ` Sergio Durigan Junior
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=20130812044819.f4bsof7l448gs4cw-nzlynne@webmail.spamcop.net \
--to=joern.rennecke@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
/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