From: Jeff King <peff@peff.net>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Stefan Beller <stefanbeller@gmail.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: How to compile Git with NDK?
Date: Tue, 23 Sep 2014 12:11:07 -0400 [thread overview]
Message-ID: <20140923161107.GB20624@peff.net> (raw)
In-Reply-To: <CAHd499C0XJDwNa3n3bzK7hu6iRunV1d=nvbqi+2pyoB8uSzDFA@mail.gmail.com>
On Tue, Sep 23, 2014 at 07:47:11AM -0500, Robert Dailey wrote:
> But if I type just 'make', I don't see how it will know where my ARM
> toolchain is. I'll read the INSTALL file in the meantime.
It won't. If you are cross-compiling you'll have to specify CC and LD
manually, plus a host of other settings. We usually pick pretty sane
defaults (which is why you can get away without running autoconf), but
they're not going to be reasonable for cross-compiling. If you do go the
non-autoconf route, you'd probably want to try building with "make
uname_S=whatever" to override our defaults (see config.mak.uname for an
idea of which uname variables we look at).
In your original report:
> >> fe@BLD01:~/code/git$ autoconf
> >> fe@BLD01:~/code/git$ ./configure --prefix=/home/fe/git-arm
> >> --build=x86_64-linux-gnu --host=arm-linux-androideabi
> >> configure: Setting lib to 'lib' (the default)
> >> configure: Will try -pthread then -lpthread to enable POSIX Threads.
> >> configure: CHECKS for site configuration
> >> checking for arm-linux-androideabi-gcc... arm-linux-androideabi-gcc
> >> checking whether the C compiler works... no
> >> configure: error: in `/home/fe/code/git':
> >> configure: error: C compiler cannot create executables
> >> See `config.log' for more details
Autoconf couldn't even build a simple hello-world with the compiler you
specified. So the first step would probably be to figure that out. What
does config.log say?
-Peff
prev parent reply other threads:[~2014-09-23 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 19:04 How to compile Git with NDK? Robert Dailey
2014-09-22 21:22 ` Stefan Beller
2014-09-23 12:47 ` Robert Dailey
2014-09-23 12:52 ` Robert Dailey
2014-09-23 16:13 ` Jeff King
2014-09-23 16:11 ` Jeff King [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=20140923161107.GB20624@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=rcdailey.lists@gmail.com \
--cc=stefanbeller@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.