@mistydemeo actually it is the contrary, the flags we add aren't expected by configure so it messes the tests.
In the build, qt handles all the flags correctly and we just duplicate the arch flag.

This PR is an answer to https://github.com/mxcl/homebrew/issues/17352, which also explain why I tend to speak in abstracts.
Qt is a direct application of the new feature, handling non standard universal binaries, because it is a non standard universal build.
CMake would be another and the mentioned issue shows that other formulae also preset non-standard universal binary (llvm I think)
I also fixed another superenv bug, "Xarched args" were simply removed, which broke Qt, but could also break other formula relying on -Xarch.
And also, anything that modifies superenv needs to be considered as something that can be used by other formula.
You can see what happens to qt with ```ENV.universal_binary```, using ```-verbose``` passed to configure.
(Some test fail where they work perfectly in normal qt build and with this new fix, xcodeversion, dwarf2 and -Xarch (before building qmake) if I remember well)
Debug and optimization creeped into the discussion, because of the previous hack which disabled some optimization and are no longer needed with the fixed -Xarch support, and because I wondered why we strip all debug info. That's should be discussed somewhere else since it isn't the purpose of this PR, do whatever you want as for ```-no-sse3 -no-3d-now``` (bottle, always, never)
I leave on holidays tomorrow, so feel free to play with the code yourselves.