[Bug target/60821] gcc 4.8 on MacOS fails depending on -arch order

[a.h.jaffe at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60821

--- Comment #4 from a.h.jaffe at gmail dot com ---
(In reply to Marek Polacek from comment #3)
> Whoops, sorry.  I better let Darwin folks look at it.

Ah, but in fact *I* misunderstood. There's a difference between the FSF and
Apple versions: 

"FSF GCC on Darwin does not create “fat” object files; it creates an object
file for the single architecture that GCC was built to target"

So I still think there's at least a "misfeature" in the sense that there should
be a more graceful failure here, but in some sense the docs are right.

However, a more general question: WHY doesn't FSF gcc have this capability?