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] New: gnu debugger ARM Android compilation
Date: Fri, 22 Nov 2013 17:45:00 -0000	[thread overview]
Message-ID: <bug-16206-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=16206

            Bug ID: 16206
           Summary: gnu debugger ARM Android compilation
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: sfence.software at gmail dot com

Created attachment 7296
  --> http://sourceware.org/bugzilla/attachment.cgi?id=7296&action=edit
diff patch of changes which I have done

Here is some problems with compilation of gdb on Android by native gcc compiler
4.8.

I have fixed this problems with my knowledge.

I add path of differences I had to do to fix it.
To fix one problem, it was easier way for my to add preprocessor directive to
android system header.

Feel free to ask me about everything. I can share my experiences with gdb
Android compilation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-11-22 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 17:45 sfence.software at gmail dot com [this message]
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

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@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).