Make configure work for gcc targets (e.g armv7a-unknown-linux-gnu)

[GoogleCodeExporter]

the current configure doesn't support gcc targets for anything but plain x86 
and amd64.

I think the code might get simplified.

Original issue reported on code.google.com by luca.bar...@gmail.com on 16 Jul 2010 at 2:50

[GoogleCodeExporter]

Original comment by iss...@webmproject.org on 16 Mar 2011 at 2:51

[GoogleCodeExporter]

This issue is pretty old, and so has become a gift to me thanks to a lovely 
automated script.

Anyway, first, sorry this hung around for so long.  Second, configure --help 
for libvpx HEAD shows:

    armv5te-linux-rvct       armv5te-linux-gcc        armv5te-none-rvct
    armv5te-symbian-gcc
    armv6-darwin-gcc         armv6-linux-rvct         armv6-linux-gcc
    armv6-none-rvct          armv6-symbian-gcc
    iwmmxt-linux-rvct        iwmmxt-linux-gcc
    iwmmxt2-linux-rvct       iwmmxt2-linux-gcc
    armv7-darwin-gcc         armv7-linux-rvct         armv7-linux-gcc
    armv7-none-rvct
    mips32-linux-gcc
    ppc32-darwin8-gcc        ppc32-darwin9-gcc        ppc32-linux-gcc
    ppc64-darwin8-gcc        ppc64-darwin9-gcc        ppc64-linux-gcc
    sparc-solaris-gcc
    x86-darwin8-gcc          x86-darwin8-icc          x86-darwin9-gcc
    x86-darwin9-icc          x86-linux-gcc            x86-linux-icc
    x86-solaris-gcc          x86-win32-gcc            x86-win32-vs7
    x86-win32-vs8            x86-win32-vs9
    x86_64-darwin9-gcc       x86_64-darwin10-gcc      x86_64-linux-gcc
    x86_64-linux-icc         x86_64-solaris-gcc       x86_64-win64-vs8
    x86_64-win64-vs9
    universal-darwin8-gcc    universal-darwin9-gcc
    generic-gnu

Looking it over I think this issue has been dealt with, and simply needs 
closing.  Agreed, or am I missing something?

Thanks!

Original comment by tomfine...@google.com on 18 Mar 2011 at 4:06

• Changed state: Accepted
• Added labels: Component-libvpx, Priority-Medium, Type-Enhancement

[GoogleCodeExporter]

This is currently supported via the various targets listed above, and/or the 
CROSS environment variable:

  $ CROSS=armv7a-unknown-linux-gnu- ./configure --target=armv7-linux-gcc ...

Unless you're talking about auto-detection when building on an ARM host maybe?

Original comment by jkoles...@google.com on 11 Jul 2011 at 3:13

• Changed state: Invalid