Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiong Wang <jiwang@tilera.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC/TileGX 1/2] fix gdbserver build failure
Date: Tue, 17 Sep 2013 12:33:00 -0000	[thread overview]
Message-ID: <52384C0E.1070808@tilera.com> (raw)
In-Reply-To: <20130917123042.GD3132@adacore.com>

于 2013/9/17 20:30, Joel Brobecker 写道:
>> TileGX gdbserver build failed on native board.
>>
>> "srv_tgtobj“ in gdbserver/configure.src not updated.
>>
>>
>> gdbserver/ChangeLog:
>>
>> * configure.srv (srv_tgtobj): Remove linux-osdata.o, add linux-tile-low.o.
>>
>> please review.
> I am trying to understand the circumstances that lead to the failure,
> and it's been made harder due to the lack of information. After some
> investigation, my guess is that you're getting some duplicate symbols
> because linux-osdata.o" is already in srv_tgtobj. Is that correct?
> If yes, this part of the patch is OK, obvious even (once explained!).

yes, exactly this error.


>
> I don't understand, however, what difference adding linux-tile-low.o
> makes in terms of build failure.  Again, I have been trying to figure
> out what lead to the failure, and searched our recent past, but could
> not find anything. I know the change makes complete sense, but if not
> logically tied to the build failure you are mentioning, I think we
> should, if nothing else, document that fact for future archival, and
> also commit this part of the change separately.
>
>> diff --git a/gdb/gdbserver/configure.srv b/gdb/gdbserver/configure.srv
>> index 6eb5a8a..f65dd10 100644
>> --- a/gdb/gdbserver/configure.srv
>> +++ b/gdb/gdbserver/configure.srv
>> @@ -340,7 +340,7 @@ case "${target}" in
>>   			;;
>>     tilegx-*-linux*)	srv_regobj=reg-tilegx.o
>>   			srv_regobj="${srv_regobj} reg-tilegx32.o"
>> -			srv_tgtobj="$srv_linux_obj linux-osdata.o"
>> +			srv_tgtobj="$srv_linux_obj linux-tile-low.o"
>>   			srv_linux_regsets=yes
>>   			srv_linux_thread_db=yes
>>   			;;
>


  reply	other threads:[~2013-09-17 12:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  9:23 [RFC/TileGX 1/6] fix args alignment bug Jiong Wang
2013-01-18 13:14 ` Joel Brobecker
2013-01-18 15:00   ` Jiong Wang
2013-01-22 10:28     ` Jiong Wang
2013-01-29 14:49       ` Jiong Wang
2013-01-30  4:34         ` Jiong Wang
2013-01-30  5:47           ` Joel Brobecker
2013-01-30  5:55             ` Jiong Wang
2013-02-08 18:33     ` Joel Brobecker
2013-09-17  3:11 ` [RFC/TileGX 1/2] fix gdbserver build failure Jiong Wang
2013-09-17  3:24   ` [RFC/TileGX 2/2] fix gdbserver runtime crash Jiong Wang
2013-09-17 12:33     ` Joel Brobecker
2013-09-17 12:39       ` Jiong Wang
2013-09-17 13:22         ` Jiong Wang
2013-09-17 13:29           ` Joel Brobecker
2013-09-17 14:06             ` [COMMITTED][RFC/TileGX " Jiong Wang
2013-09-17 12:30   ` [RFC/TileGX 1/2] fix gdbserver build failure Joel Brobecker
2013-09-17 12:33     ` Jiong Wang [this message]
2013-09-17 13:21       ` Jiong Wang
2013-09-17 13:30         ` Joel Brobecker
2013-09-17 13:36           ` Jiong Wang
2013-09-17 13:43             ` Joel Brobecker
2013-09-17 14:04               ` [COMMITTED][RFC/TileGX " Jiong Wang
2013-09-18  1:56                 ` Yao Qi

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=52384C0E.1070808@tilera.com \
    --to=jiwang@tilera.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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