From: Robert <robert@mailueberfall.de>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Building gdb for Android using Android-ndk
Date: Wed, 23 Jan 2013 14:54:00 -0000 [thread overview]
Message-ID: <50FFF99E.6010800@mailueberfall.de> (raw)
In-Reply-To: <50FFE822.5010309@redhat.com>
Hi Pedro,
thanks for your reply.
> You're building a gdb that runs on Android? Or you want a GDBserver
> that runs on Android, but debug from your x86_64 Ubuntu host?
I am trying to build a standalone version of gdb that runs directly on
the device. It is coincidence that the error just occurs in the
gdbserver subproject. I am not aware of the internal dependencies of gdb
- may be one can simply disable the gdbserver subproject?
> So is "gcc" itself a native compiler running on Android? If not,
> then you should be seeing arm-linux-androideabi-gcc or some such
> here.
You are right, this little strange detail did not catch my attention.
Looks like the configuration was not done correctly.
Therefore I deleted everything and started from scratch. Now the build
process looks correct, but stops much earlier with an error I have seen
several times before:
arm-linux-androideabi-gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I./../include
-W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic
./getpagesize.c -o getpagesize.o
./getpagesize.c:64:1: error: redefinition of 'getpagesize'
/opt/android-standalone-toolchain/bin/../sysroot/usr/include/unistd.h:162:23:
note: previous definition of 'getpagesize' was here
I checked the log and noticed that the system checks that executed the
first time when I execute "make" contains several lines with
"checking for getpagesize... no".
I uploaded the complete make log here: http://pastebin.com/v3etd3Sa
Robert
next prev parent reply other threads:[~2013-01-23 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 9:29 Robert
2013-01-23 13:40 ` Pedro Alves
2013-01-23 14:54 ` Robert [this message]
2013-01-23 14:58 ` Pedro Alves
[not found] ` <35190382.post@talk.nabble.com>
2013-04-04 9:43 ` Pedro Alves
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=50FFF99E.6010800@mailueberfall.de \
--to=robert@mailueberfall.de \
--cc=gdb@sourceware.org \
--cc=palves@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