On Fri, Oct 14, 2022 at 06:16:27PM +0000, Andrew Cooper wrote: > On 13/10/2022 14:05, Anthony Perard wrote: > > Alternatively, we could remove the need for to generate a > > version-script, but that would mean the exported symbols won't have a > > version anymore (like before, a few versions of Xen ago). Or, we could > > use --default-symver, but the symboled would be versionned with the > > soname (e.g. "libxenctrl.so.4.16.0") instead of "VERS_4.16.0". > > It turns out that the use of VERS_* everywhere is buggy. We should have > had 'XEN$FOO' in the soname for libraries. But it's too late for the > stable ones. > > As far as the unstable libraries go, it really doesn't matter. The only > thing we care about (rightly or wrongly) is that you can't mistake the > libraries from different versions of Xen. > > --default-symver sounds like it would be ideal, and avoid writing out > temporary version scripts.
Sounds good to me, I'll rewrite the patch to use --default-symver. Hopefully, that's an old enough option. Thanks, -- Anthony PERARD
