On 10/07/2013 01:31 PM, Jeffrey Walton wrote: > Thanks Eric, > >>> I'm not sure why I'm trying to trick the build system with host=arm >>> since the host is x86_64. >> >> You're lying. You're telling configure that your compiler is on an >> arm-based host, when it is really on an x86_64-based host. > OK, thanks. > >> (I don't know the target triple for an android system, unfortunately). > Yeah, neither do I (for Mac OS X or Android). But you DO know it :) > > 3) Export the tools: > export CPP=arm-linux-androideabi-cpp > export CC=arm-linux-androideabi-cc Your --target triple is therefore: arm-linux-androideabi Autoconf-based configure files by default will attempt to use $TRIPLE-cc, without you having to export CC and lots of other variables, if you just tell it the right --target name, and if all of your cross toolchain is consistently named as $TRIPLE-tool. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
