public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sfence.software at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/16206] gnu debugger ARM Android compilation
Date: Sat, 23 Nov 2013 09:27:00 -0000 [thread overview]
Message-ID: <bug-16206-4717-XdfAVcfCvp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16206-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16206
--- Comment #3 from SFENCE <sfence.software at gmail dot com> ---
(In reply to Yao Qi from comment #2)
> (In reply to SFENCE from comment #1)
> > Created attachment 7297 [details]
> > diff path without useless informations
> >
> > For better clear arrangement...
>
> The changes look a little hacky and they may have some effects on other
> targets.
>
> These patches work, but I am afraid they are not acceptable. If you want to
> have a try, please send them to different mail lists because they belong to
> different projects.
> - Changes in bfd should be sent to binutils mailing list,
> - Changes in libiberty should be sent to gcc mailing list,
> - Changes in readline should be sent to list of project readline. Once it
> is accepted, backport it to GDB
> - Changes in gdb should be sent to gdb mailing list.
I have just compiled actual release of readline projects without any problems
on ARM Android. But the change I have added to readline in GDB source missed
here. It is probably solved by configure.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2013-11-23 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 17:45 [Bug build/16206] New: " sfence.software at gmail dot com
2013-11-22 22:13 ` [Bug build/16206] " sfence.software at gmail dot com
2013-11-23 7:21 ` qiyao at gcc dot gnu.org
2013-11-23 9:27 ` sfence.software at gmail dot com [this message]
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=bug-16206-4717-XdfAVcfCvp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).