Hello Christian & Michael, Michael Biebl <email@example.com> (2015-06-08): > Am 07.06.2015 um 23:59 schrieb Christian Kastner: > > On 2015-06-07 23:22, Cyril Brulebois wrote: > >> Christian Kastner <firstname.lastname@example.org> (2015-06-07): > >> | @@ -1,4 +1,5 @@ > >> | libcap.so.2 libcap2 #MINVER# > >> | + __cap_lookup_name@Base 1:2.24-9 > >> | _cap_names@Base 1:2.10 > >> | _libcap_strdup@Base 1:2.10 > > >> More seriously, I'm not sure it should be exposed in the shared library, > >> so you may want to unexpose it instead of just adding it to the symbols > >> file. > > > > With regards to the cause listed above, I'd rather just disable this > > "feature" entirely, and (possibly, if it makes sense) add gperf as a > > B-D at a later point, and then deal with the symbol as you recommend. > > Either way resolves the current nondeterminism in the build, which is at > > the moment what bothers me the most, TBH. I'm currently toying with apt install/purge gperf for the libcap2 and systemd builds, I'll let you know once I'm done testing builds. > When you are going to tackle this, _cap_names and _libcap_strdup look > like they should be hidden as well, at least I can't find those > symbols in the header files. Yup, I spotted those funny names as well in the symbols diff, but failed to mention them in my first mail, sorry+thanks. Mraw, KiBi.
Description: Digital signature