http://bugzilla.novell.com/show_bug.cgi?id=941428
http://bugzilla.novell.com/show_bug.cgi?id=941428#c3
--- Comment #3 from Richard Biener
-dumpversion is not returning the version of gcc, it is returning '5'
The man page for gcc under -dumpversion says it returns the version, like '3.0'.
-dumpversion returns 5 which is also a version number.
-dumpversion exists so that scripts and other entities do not have to parse the output of -version, to determine the gcc version.
At present, all other vendors, the FSF upstream project, and all previous openSUSE versions are returning, at a minimum, the major.minor version value in the output of -dumpversion.
Not Debian/Ubuntu though.
On opensuse, because it returns '5', scripts that expect MAJOR.MINOR or MAJOR.MINOR.REV are now broken on opensuse, and cause a breakage. Developers on those projects view the dumpversion output a bug and a regression on opensuse that needs to be fixed.
Well, who expects major.minor at least needs to be fixed.
Because dumpversion returns '5', there's no way for anyone to determine if it has a feature or bug that exists in 5.1 but is fixed in 5.2.
Version numbers are not good for determining whether bugs are fixed. Vendors can backport patches or adjust version numbers. openSUSE always prints 4.8 for 4.8.0, 4.8.1 ... 4.8.5. It looks like -dumpversion for a reason does _not_ output the version as dumped with --version but a different one which is also used to compose version-specific path names. Note that version specific path names in openSUSE use '5' as sub-directory name, so -dumpversion has to be consistent with that. Changing this likely will projects that use -dumpversion and expect to be able to compose paths with it.
Reference: https://github.com/joyent/node/pull/25671 http://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/ 20150811220113.4a47e5cd128ff2aef78cb83b%40wi.rr.com/#msg34366574
-- You are receiving this mail because: You are on the CC list for the bug.