Right. Sorry, that was not the right reference. That site shows how to build for arm, rather than specifically for Android.
Autoconf will you the host as the prefix to the cross-compiler tools. The android tools are prefixed with "arm-eabi" (as I mentioned in a previous email), so if I run configure with "--host arm-eabi-linux-gnu", autoconf will look for "arm-eabi-linux-gnu-gcc" and fail. I don't have a thorough understanding of autoconf and cross-compiling, so I'm not entirely clear on the inner workings of all this... On Fri, Apr 23, 2010 at 11:15 AM, Samuel Thibault < [email protected]> wrote: > Shiri Azenkot, le Fri 23 Apr 2010 11:06:28 -0700, a écrit : > > Shouldn't > > > > that be > > > > --host arm-eabi-linux-gnu > > > > > > I think setting host to "arm-eabi" should be right... All the > cross-compiling > > examples for android that I've seen set host to "arm-eabi". This tells > autoconf > > to look for tools with the "arm-eabi" prefix, like "arm-eabi-gcc". > > > > This website might be useful; it shows examples of how to cross compile > a few > > libraries that use autoconf: > > > http://www.ailis.de/~k/archives/19-ARM-cross-compiling-howto.html#libraries<http://www.ailis.de/%7Ek/archives/19-ARM-cross-compiling-howto.html#libraries> > > It uses --host=arm-linux > > Samuel > _______________________________________________ > This message was sent via the BRLTTY mailing list. > To post a message, send an e-mail to: [email protected] > For general information, go to: http://mielke.cc/mailman/listinfo/brltty >
_______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
