http://bugzilla.suse.com/show_bug.cgi?id=1073210
http://bugzilla.suse.com/show_bug.cgi?id=1073210#c3
--- Comment #3 from Richard Biener ---
Yes, if you use the compiler driver then the linker gets an explicit -plugin
path.
That should also work with static libs (though the build machineries ar
commands
may fail if they are not using gcc-ar and friends).
For the purpose of tools other than ld the "old" plugin should suffice... but
yes,
the issue with compatibility exists. I thought about update-alternatives but
that's really a bad solution given the user can override things. A better
solution would be to follow how we handle libgcc_s1 and friends, thus split
out liblto_plugin.so.0 to a separate package and require some prjconf magic
when a new GCC becomes available officially.
I'll see to do that for Tumbleweed/SLE15.
Note I see no good way to update Leap other than maybe simply porting the 'gcc'
part symlinking the system compiler version.
--
You are receiving this mail because:
You are on the CC list for the bug.