g++ -print-file-name=plugin uses the full version number in the path when just the major version number is all that's required for compatibility. This means that plugins have to require the specific version of gcc and have to be rebuild after every update to gcc. For what it's worth, gcc on Ubuntu only uses the major version number ( see https://bugzilla.redhat.com/show_bug.cgi?id=1408943#c9 ).
That is the standard behavior of gcc. Ubuntu+SuSE use some hack that has never been submitted upstream.
Created attachment 1237858 [details]
gcc patch for version from OpenSUSE
Taken from http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/suse/src/gcc6-6.1.1+r238085-1.12.src.rpm
(In reply to Jakub Jelinek from comment #1)
> That is the standard behavior of gcc. Ubuntu+SuSE use some hack that has
> never been submitted upstream.
I attached the patch from OpenSUSE that I believe is changing the directory. Can that be flowed upstream?
I opened a bugzilla for gcc.
Just curious here, was there some progress?
gcc 7 in Fedora Rawhide (26) now just uses the major version as the plugin path. You can see the details in the linked to gcc bugzilla.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.