So, I finally got a chance to look at this. It sounds like you're taking a significantly different approach than we had discussed earlier.
What we had talked about is parsing the output of $CC. For example asking gcc what tripple it was built for and going from there. But what you did is assume that the gcc path encodes the tripple with the special case of supporting -m32 assuming that it is the first option in $CC (and not say in $CFLAGS). It looks like this was probably a bit easier to code, but looks like it has the following weaknesses: * Assumes that -m64 is always on a x86_64 system rather than using gcc -m64 to build for x86_64 on an 686 system. * assumes that -m32 and -m64 are only used on x86 architectures * Mishandles setups where rather than set all the compiler variables, a directory including cross tools is prepended to PATH Are there advantages beyond implementation simplicity over what we talked about previously?
