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 13:36:00 -0000 [thread overview]
Message-ID: <52385AEF.5070404@tilera.com> (raw)
In-Reply-To: <20130917133023.GG3132@adacore.com>
äº 2013/9/17 21:30, Joel Brobecker åé:
>>>>> 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.
>> is this OK to commit ?
> Only the part that remove linux-osdata.o for now.
>
> I expect that you'll be able to commit the other half, but after
> having explained in detail what this fixes. I suspect that this
> enables some features, rather than fix a failure.
linux-tile-low.o is the target file of TileGX. (it's name is confusing ?)
previous commit by the following wrongly removed the tilegx target file.
commit f7fc28008a4d76dd6e55eb77070eb18e956406a9
Author: Luis Machado <luisgpm@br.ibm.com>
Date: Thu Aug 22 23:46:27 2013 +0000
- srv_tgtobj="linux-low.o linux-tile-low.o linux-osdata.o linux-procfs.o"
- srv_tgtobj="${srv_tgtobj} linux-ptrace.o"
+ srv_tgtobj="$srv_linux_obj linux-osdata.o"
>
next prev parent reply other threads:[~2013-09-17 13:36 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
2013-09-17 13:21 ` Jiong Wang
2013-09-17 13:30 ` Joel Brobecker
2013-09-17 13:36 ` Jiong Wang [this message]
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=52385AEF.5070404@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