From: Jeffrey Walton <noloader@gmail.com>
To: Kai Ruottu <kai.ruottu@wippies.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Build a cross compiler for Android target (arm)
Date: Mon, 17 Oct 2011 06:45:00 -0000 [thread overview]
Message-ID: <CAH8yC8n6jrCsXuGhA-c++13WA0cQ485zcsf7bq4bmeq3jpctaQ@mail.gmail.com> (raw)
In-Reply-To: <4E9BCC09.3030701@wippies.com>
On Mon, Oct 17, 2011 at 2:32 AM, Kai Ruottu <kai.ruottu@wippies.com> wrote:
> 15.10.2011 12:41, BERTRAND Joel kirjoitti:
>
>> I'm trying to build a cross compiler for Android target as I want to
>> obtain a Fortran compiler.
>>
>> Of course, I have installed android ndk to have sysroot.
>> Build process stops with :
>>
>> checking whether the
>> /home/bertrand/android/ndk/compilers/gcc-build/./gcc/xgcc
>> -B/home/bertrand/android/ndk/compilers/gcc-build/./gcc/
>> -B/home/bertrand/android/ndk/compilers/arm-android-eabi/bin/
>> -B/home/bertrand/android/ndk/compilers/arm-android-eabi/lib/ -isystem
>> /home/bertrand/android/ndk/compilers/arm-android-eabi/include -isystem
>> /home/bertrand/android/ndk/compilers/arm-android-eabi/sys-include linker
>> (/home/bertrand/android/ndk/compilers/gcc-build/./gcc/collect-ld)
>> supports shared libraries... yes
>> checking dynamic linker characteristics... no
>> checking how to hardcode library paths into programs... immediate
>> checking for shl_load... configure: error: Link tests are not allowed
>> after GCC_NO_EXECUTABLES.
>> make[1]: *** [configure-target-libstdc++-v3] Erreur 1
>
> Ok, you have the GCC binaries ready (in $build/gcc) and also
> libgcc (in $build/libgcc) and then your build crashes when
> trying to configure libstdc++-v3 ... The C parts are OK, but
> getting the C++ library fails. So what would be the sane
> reaction in this situation?
>
> For me it would be to try to compile and link a simple "Hello
> World" app with the new GCC... But maybe Android is too weird
> for this, no experience about whether it even supports simple
> "console" apps in a terminal window, requiring some really
> complex application as that "Hello World".
Google has their own stdc and stdc++, which has some compilation
problems. Search the Android NDK group
(http://groups.google.com/group/android-ndk) and the Android Issue
List (http://code.google.com/p/android/issues/list). See, for example,
http://code.google.com/p/android/issues/detail?id=14559.
Jeff
next prev parent reply other threads:[~2011-10-17 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 9:41 BERTRAND Joel
2011-10-17 6:33 ` Kai Ruottu
2011-10-17 6:45 ` Jeffrey Walton [this message]
[not found] ` <4E9BDC91.4010801@systella.fr>
2011-10-17 7:44 ` BERTRAND Joel
2011-10-17 8:05 ` BERTRAND Joel
2011-10-17 7:44 ` BERTRAND Joel
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=CAH8yC8n6jrCsXuGhA-c++13WA0cQ485zcsf7bq4bmeq3jpctaQ@mail.gmail.com \
--to=noloader@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kai.ruottu@wippies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).