Xcode buries /usr/bin/gcc deep beneath Xcode.app/Content/Developer

Question

How do I get GCC, and the rest of the compiler utilities that come with Xcode to show up in the standard /usr/bin directory?
I downloaded and installed Xcode from the Apple App store.  When the installation completed, Xcode had buried the standard compiler components that are typically in /usr/bin deep under the Applications directory at /Applications/Xcode.app/Content/Developer/usr/bin.
This is Xcode 5.0 (5A1413) and OS 10.8.5.

Answer 1

A.Rick wrote:
I am attempting to use a variety of tools that assume on a traditional Unix/Linux environment, such as Maven, Eclipse, CUDA etc.  The fact that a Mac has a real Unix underneath all that makeup was a key factor in my purchase decision.
There is nothing "traditional Unix" about those tools. I didn't even know what Maven was. It is apparently some Java thing. I can assure you that UNIX predates Java by many years. UNIX is nothing but a certification that is applied on top of an operating system. It can't really be said that the Mac has a "real Unix underneath". The Mac is a certified UNIX operating system and has a command-line and POSIX interface, but underneath it is just as Mac as it appears - i.e. not Linux.
I have the tools that I am after.  They are just in the wrong place.  Having a tool, with a different name, that acts like GCC, or Make, etc. doesn't help me when the build environment that I am working with assumes the original Unix tool.
So, is it true that the only way I that will be able to get the orignal behavior is to copy everything that is beneath /Applications/Xcode.app/Content/Developer/usr/bin up to the real /usr/bin?
Depending on your operating system, you may be able to have Xcode just install command-line tools. I think Mavericks will install them automatically (if you try to use them) even without Xcode. You can also download the command-line tools installer package from the Apple Developer site.
To quote the GNU folks, GNU's not UNIX. If you want to use GNU tools, you will have to ask the GNU people to port them to the Mac. They have never, ever completely done that. GNU has always relied in some form on lower-level Xcode tools. Then, once GNU kicked Apple to the curb with GPLv3, Apple wrote its own compiler. You can use the command-line as much as you want, but the commands are going to be slightly different that what you are used to on Linux.
If you want to use Linux, then you should use Linux. The Mac is different. I think it is better than Linux. The Linux people disagree.