Re: libgclib - symbol file - please kindly educate me
Hi Steffen,
the patch you get from dh_makeshlibs needs to be edited. You simply
sed -i 's/-1$//' debian/libgclib2.symbols
should do the trick.
Hope this helps
Andreas.
On Sat, Aug 08, 2020 at 11:39:24PM +0200, Steffen Möller wrote:
> Hello,
>
> to get the build process to first not fail and then be quiet, I changed
> the .symbols file as follows:
>
> diff --git a/debian/libgclib2.symbols b/debian/libgclib2.symbols
> index 6bef43a..aef012c 100644
> --- a/debian/libgclib2.symbols
> +++ b/debian/libgclib2.symbols
> @@ -25,7 +25,8 @@libgclib.so.2 libgclib2 #MINVER#
> _Z10g2bit2baseh@Base 0.11.4
> _Z10gcdb_allocj@Base 0.11.4
> _Z10getFileExtPKc@Base 0.11.4
> - _Z10getOvlCodeR6GffObjS0_Rib@Base 0.11.4
> + _Z10getOvlCodeR6GffObjS0_Rib@Base 0.11.10-1
> + _Z10getOvlCodeR6GffObjS0_Ribi@Base 0.11.10-1
> _Z10parseFloatRPcRf@Base 0.11.4
> _Z10replaceStrRPcS_@Base 0.11.4
> _Z10startsWithPKcS0_@Base 0.11.4
> @@ -78,12 +79,15 @@libgclib.so.2 libgclib2 #MINVER#
> _Z14gfo_cmpRefByIDPvS_@Base 0.11.4
> _Z14translateCodonPKc@Base 0.11.4
> _Z15printEditScriptP12GXEditScript@Base 0.11.4
> - _Z15transcriptMatchR6GffObjS0_Ri@Base 0.11.4
> + _Z15transcriptMatchR6GffObjS0_Ri@Base 0.11.10-1
> + _Z15transcriptMatchR6GffObjS0_Rii@Base 0.11.10-1
> _Z15uint32_pack_bigPcj@Base 0.11.4
> _Z16BED_addAttributeP8_IO_FILERiPKcz@Base 0.11.4
> _Z16DefLTCompareProcI4GSegEiPvS1_@Base 0.11.4
> _Z16gthreads_errExitiPKc@Base 0.11.4
> - _Z16singleExonTMatchR6GffObjS0_Ri@Base 0.11.4
> + _Z16singleExonTMatchR6GffObjS0_Ri@Base 0.11.10-1
> + _Z16singleExonTMatchR6GffObjS0_Rii@Base 0.11.10-1
> + _Z15transcriptMatchR6GffObjS0_Rii@Base 0.11.10-1
> _Z17GreedyAlignRegionPKciiS0_iiP16CGreedyAlignDataP8CAlnTrimb@Base 0.11.4
> _Z17GreedyAlignRegionPKciiS0_iiiiiP16CGreedyAlignDataP8CAlnTrimb@Base
> 0.11.4
> _Z17gcvt_endian_setupv@Base 0.11.4
>
> I have no idea why there is now a -1 attached to the version. I just
> know that it does not work without it.
>
> Can I upload as is?
>
> Best,
>
> Steffen
>
>
--
http://fam-tille.de
Reply to: