Quote:
Originally Posted by knc1
Doing that might (probably will) lead to problems with the other components of the tool-chain.
If you browse the tool-chain tree, you will find "gcc" in two places ...
One, under an "ARCH qualified path / bin"
One, where the "ARCH qualifier" is part of the "gcc" file name.
You want the full, absolute, path to the "ARCH qualified path / bin" first in your path search order.
Listing the contents of that "ARCH qualified path / bin" will show just how many components are included in the tool-chain.
Ah, another bit of related trivia: the application "gcc" is not the compiler. It is the command line option processor "front end" to the tool-chain. It in turn munges the options and calls the various other components in that "ARCH qualified path / bin" to get the various parts of the compile done.
At which point the tool-chain behavior usually turns into crap when its intial access was via a (shortened) symbolic link.
|
Ar! I see what you mean
Rightyo then, I will do a tidyup before I try any statically charged builds and call from the fully qualified name for now then!
Thanks knc1