Hi Eriberto,
> Ok. I can see the problem here. However, I can't have time (because
> the freeze stage) to do tests (I need tests to understand better the
> process to split these symbols, uploading to experimental before
> unstable). So, I think that the best way is remove all optional
> entries
Hi Hilko,
Sorry for my delay. I had some problems in my work.
2017-01-19 9:37 GMT-02:00 Hilko Bengen :
> Hi Eriberto,
>
> I see that you have simply marked many symbols optional instead of
> splitting the .symbols file. Please reconsider that decision.
>
> You approach works
Hi Eriberto,
I see that you have simply marked many symbols optional instead of
splitting the .symbols file. Please reconsider that decision.
You approach works in the sense that the package no longer fails to
build on architectures where not all defined symbols aren't present.
However, there
2017-01-14 14:37 GMT-02:00 Hilko Bengen :
> Eriberto,
>
> please take a look at the commit I pushed to
> https://anonscm.debian.org/git/forensics/sleuthkit.git, specifically
> 19ed029000b71d6900368294130c4c919aff369d. I have split the .symbols file
> into three files (common,
Eriberto,
please take a look at the commit I pushed to
https://anonscm.debian.org/git/forensics/sleuthkit.git, specifically
19ed029000b71d6900368294130c4c919aff369d. I have split the .symbols file
into three files (common, 32bit, 64bit) and made a few classes of
symbols optional.
Cheers,
-Hilko
Control: reopen 850828 !
Hi,
Em terça-feira, 10 de janeiro de 2017, Hilko Bengen
escreveu:
> control: tag -1 patch
>
> Hi,
>
> here is a .symbols file for which I have replaced the mangled C++
> symbols with their unmangled versions. I have also added a couple of new
>
control: tag -1 patch
Hi,
here is a .symbols file for which I have replaced the mangled C++
symbols with their unmangled versions. I have also added a couple of new
symbols, assuming that they have been added in 4.3.0 (not 4.3.1).
Cheers,
-Hilko
libtsk.so.13 libtsk13 #MINVER#
7 matches
Mail list logo