Thanks for the responses.
Firstly, the option to use
OPENSSL_ia32cap="~0x200000000000000" clamtk
instead of
OPENSSL_ia32cap=0 clamtk
does work. I don't know if that helps anyone.
If the cpuinfo is still useful please let me know which specific bit is wanted
I will look at what I reported on clamtk and state that it's not a clamtk or
debian fault.
And I'll look at reporting on ubuntu/xubuntu if I think it will be useful.
Regards Tim
On 02/03/16 11:09, Sebastian Andrzej Siewior wrote:
On 2016-03-02 10:01:25 [+0000], Tim Passingham wrote:
This was some time ago, and my memory is not good. Is there some problem
with the solution that works?
This is not a solution, it is a workaround. You can also close the
upstream (clamtk) bug report because it is not a clamtk bug.
I find the debian bug reporting by email very strange - Ivery much prefer
the forum-based method. I can't see the whole bug report chain, so I have
no context, and I've no idea if we have exchanged information before or not.
The full chain is at
http://bugs.debian.org/793557
I also don't know if I should have done a Reply All or not. Sorry.
No, it is fine. Regarding xubuntu: If the latest (up-to-date) version of
openssl on your system still triggers the bug then open a bug *there* and
point them to this bug report. Kurt's message [0] is very informative on
what needs to be done.
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793557#132
Tim
Sebastian
--
email: t...@tim-passingham.co.uk
