On Saturday 04 April 2009 23:42:54 Daniel Pielmeier wrote:
> Joseph schrieb am 04.04.2009 22:48:
> > Is there a way to verify GCC version program was compiled with?
> > I just want to check if all the programs were compiled with latest GCC
> > version as I'm getting an errors at time to time.
>
> I don't think it is possible to get the compiler or it's version used
> for a specific program. If you are upgrading the compiler it is
> advisable to recompile the complete system so all programs are compiled
> with the same compiler version. Take a look at the gcc upgrading guide
> [1] for the necessary steps you need to follow.
>
> [1] http://www.gentoo.org/doc/en/gcc-upgrading.xml

This is complete nonsense advice. There is absolutely no need to rebuild the 
entire system every time you upgrade compilers, and whoever told you that is 
flat out wrong. If the gentoo docs told you that, then they are wrong, or 
misplaced, or the person writing them is overcautious to the point of being 
ridiculous. If this advice really was true, then a whole lot of stuff would 
break all over the world:

- every Windows box on the planet would need a complete reinstall whenever a 
Windows Update happened (Yes, Microsoft does upgrade their compiler!)
- third party apps would not run, as you have no way of knowing if Oracle's 
compiler is the same as yours (and you don't even have a guarantee that Oracle 
uses gcc). My Oracle instance at work is working just fine and I know for a 
fact the compilers used for it and SuSE are not even in the same version 
series.
- Compiling any package locally could not work on a binary distro. But they 
do.

There are *some* special cases where the gcc devs break stuff at an ABI level 
between versions (usually related to C++ not to C). These are well known and 
heavily documented - the toolchain devs make sure of this. 3.3 to 3.4 was such 
a case, there was another minor case early in the gcc-4 series. By no means do 
this mean that the fix for those cases must now be applied every time.

-- 
alan dot mckinnon at gmail dot com

Reply via email to