|
From: Rich C. <rc...@wi...> - 2015-08-13 16:15:05
|
On Wed, 12 Aug 2015 06:52:33 -0500 Rich Coe <rc...@wi...> wrote: > On Wed, 12 Aug 2015 07:10:57 +0100 > Tom Hughes <to...@co...> wrote: > > On 12/08/15 04:01, Rich Coe wrote: > > > > > This looks like it is opensuse specific, but gcc-5 -dumpversion returns > > > a single digit (5) for gcc 5.1.1. > > > > Shouldn't you be betting opensuse to fix this? It doesn't do that on Fedora: > > > I wrote BZ#941428 https://bugzilla.novell.com/show_bug.cgi?id=941428 to track it. BZ closed wontfix. Thoughts? --- Comment #4 from Michael Matz <ma...@su...> --- Yes, this works as designed, and indeed -dumpversion can be (and is) used for path composition. If you compare filelists and -dumpversion output of different gcc compilers you'll see that paths in opensuse packages use the version differentiator as returned by -dumpversion, _not_ as in the output of --version, this is the same on debian (and I think fedora). It's just that some packagers included the microversion in it and we don't. With the version scheme change of GCC 5 the microversion went away, basically shifting all number positions one up, so now we don't include the minor version anymore in directory paths, and hence also not in -dumpversion, so in the future it'll only be a single number. Read http://gcc.gnu.org/develop.html#num_scheme for a little background on the changed versioning scheme. Yes, this upstream change causes some hassle in packages trying to parse the version, that's unfortunate but was to be expected. -- Rich Coe rc...@wi... |