so basically you copied the actual binary under a different name, so as blitz assumed it had found the 'right' version? technically this is exactly the same as a symlink (symlinks are pseudo files that redirect to actual files, so when you call a symlink your actually calling the binary (or whatever) that the symlink refers to - thus by creating a symlink of gcc-3.3 and pointing it to gcc, your actually doing the same as copying gcc and renaming it to gcc-3.3, only your saving a huge amount of disk space in the process).
unfortunately this is what isn't working for me, and the above posts suggest this is largely due to my use of a 64bit kernel, binaries, and libraries.
cheers anyway.
unfortunately this is what isn't working for me, and the above posts suggest this is largely due to my use of a 64bit kernel, binaries, and libraries.
cheers anyway.