Displaying 2 results from an estimated 2 matches for "nbd_new_symbol".
2019 Jul 27
3
[PATCH libnbd] lib: Use symbol versions.
...adds support for symbol versions. It is based on what
libvirt does.
The generated syms file looks like:
LIBNBD_1.0 {
global:
nbd_...;
nbd_...;
local: *;
};
In a future stable 1.2 release, new symbols would go into a new
section which would look like this:
LIBNBD_1.2 {
global:
nbd_new_symbol;
nbd_another_new_symbol;
local: *;
} LIBNBD_1.0;
In my testing the ‘local:’ label is needed. For some reason libvirt
doesn’t use it.
The change appears to be working in as much as I can see the symbol
versions appearing, and the test/example programs continue to run.
$ nm -D --with-symbol...
2019 Jul 29
0
Re: [PATCH libnbd] lib: Use symbol versions.
...The generated syms file looks like:
>
> LIBNBD_1.0 {
> global:
> nbd_...;
> nbd_...;
> local: *;
> };
>
> In a future stable 1.2 release, new symbols would go into a new
> section which would look like this:
>
> LIBNBD_1.2 {
> global:
> nbd_new_symbol;
> nbd_another_new_symbol;
> local: *;
> } LIBNBD_1.0;
>
> In my testing the ‘local:’ label is needed. For some reason libvirt
> doesn’t use it.
We do use it - just note that src/libvirt_public.syms is *not* what
is used to link. We combine that file with libvirt_private....