https://bugs.kde.org/show_bug.cgi?id=512291
--- Comment #3 from Vladimír Marek <[email protected]> --- Hi, thank you for getting back to me. Correct, we do not have valgrind on sparc (sadly). You can test it by removing /usr/include/sys/crypto/ioctl.h and trying to compile valgrind. That ioctl.h was removed only recently, so it will take some time before the change appears even at paying customers machines. However my patch is safe to apply even now. The sys/crypto/ioctl.h delivers some definitions and structures, but no one is using them. The crypto functionality was removed during 2018, now we are removing just the unused header files. I have updated valgrind which is being built for Solaris to 3.26 and updated the patch accordingly. You can see that we are using the patch too here: https://github.com/oracle/solaris-userland/commit/fb09518777dae7f67de40689a7bb51e1be4f73f2 . Latest free release available is the CBE release 11.4.81 at https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html . It requires oracle account though (even though it is free). And you must have ksh and run ugly script (sigh). And it does not work on Linux as I just tried (more sigh). But if you run it it will create IPS repo from which you can update Solaris to fairly recent build. Longer story follows. Back in time Sun Microsystems did release T1 (codename Niagara) which had hardware support for cryptography. There was big BUT, the instructions for that were limited to priviledged space only, meaning only kernel was able to run them. So Solaris gained new driver called 'crypto' though which applications were able to use it. And new syscalls. Because one had to pass data between userspace and kernel it was slow. So eventually T4 came which allowed to call crypto functions directly from user space. Wikipedia says 2005. Since then we do not need the crypto kernel module and syscalls. Originally we thought we could use the crypto module for all kinds of crypto work (even on x86) but in reality this never happened. So during 2018 the crypto framework was removed and about a month ago colleague of mine did some cleanup and removed the headers. Which in turn broke valgrind build which is why I got involved and learned about the whole history :) It could be argued that old Solaris 10 installations still have the crypto functionality (S10 is 20 years old too ...). We could make autotools detect the presence of /usr/include/sys/crypto/ioctl.h. If that is something you are more likely to accept I'm happy to go that route too. Personally I do not think that it is practical. -- You are receiving this mail because: You are watching all bug changes.
