From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32175 invoked by alias); 17 Oct 2011 06:45:15 -0000 Received: (qmail 32161 invoked by uid 22791); 17 Oct 2011 06:45:13 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-vw0-f47.google.com (HELO mail-vw0-f47.google.com) (209.85.212.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Oct 2011 06:44:59 +0000 Received: by vwe42 with SMTP id 42so1525762vwe.20 for ; Sun, 16 Oct 2011 23:44:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.112.135 with SMTP id iq7mr19259226vdb.51.1318833898741; Sun, 16 Oct 2011 23:44:58 -0700 (PDT) Received: by 10.220.163.9 with HTTP; Sun, 16 Oct 2011 23:44:58 -0700 (PDT) Reply-To: noloader@gmail.com In-Reply-To: <4E9BCC09.3030701@wippies.com> References: <4E995534.6040903@systella.fr> <4E9BCC09.3030701@wippies.com> Date: Mon, 17 Oct 2011 06:45:00 -0000 Message-ID: Subject: Re: Build a cross compiler for Android target (arm) From: Jeffrey Walton To: Kai Ruottu Cc: gcc-help@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00138.txt.bz2 On Mon, Oct 17, 2011 at 2:32 AM, Kai Ruottu 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