> ? ?This is really tricky. We would have to parse the output from the 
> compiler/linker and "understand automatically" the problem so we can report 
> it back to the user. In general this is impossible. We could, however, for 
> example handle THIS case by looking for the string: ?"file was built for 
> unsupported file format which is not the architecture being linked" and print 
> an error message specific to that string. The problem is if Apple or the 
> compiler writes change one word in their error message our string search no 
> longer works.

I understand.  Since I'm new to this build system, I didn't think to
look in the log for some reason.  Maybe you could just say, see the
log for more info?

wes

Reply via email to