1. 24 Sep, 2017 1 commit
  2. 16 Sep, 2017 5 commits
  3. 14 Aug, 2017 1 commit
  4. 23 May, 2017 2 commits
  5. 24 Apr, 2017 5 commits
  6. 21 Apr, 2017 1 commit
  7. 19 Apr, 2017 1 commit
  8. 05 Apr, 2017 1 commit
  9. 30 Mar, 2017 6 commits
  10. 30 Dec, 2016 1 commit
  11. 26 Dec, 2016 1 commit
  12. 21 Nov, 2016 1 commit
  13. 24 Oct, 2016 2 commits
    • Lasse Collin's avatar
      Update THANKS. · a01794c5
      Lasse Collin authored
      a01794c5
    • Lasse Collin's avatar
      tuklib_cpucores: Add support for sched_getaffinity(). · df8f446e
      Lasse Collin authored
      It's available in glibc (GNU/Linux, GNU/kFreeBSD). It's better
      than sysconf(_SC_NPROCESSORS_ONLN) because sched_getaffinity()
      gives the number of cores available to the process instead of
      the total number of cores online.
      
      As a side effect, this commit fixes a bug on GNU/kFreeBSD where
      configure would detect the FreeBSD-specific cpuset_getaffinity()
      but it wouldn't actually work because on GNU/kFreeBSD it requires
      using -lfreebsd-glue when linking. Now the glibc-specific function
      will be used instead.
      
      Thanks to Sebastian Andrzej Siewior for the original patch
      and testing.
      df8f446e
  14. 30 Jun, 2016 1 commit
  15. 16 Jun, 2016 1 commit
  16. 10 Apr, 2016 2 commits
  17. 13 Mar, 2016 1 commit
    • Lasse Collin's avatar
      liblzma: Disable external SHA-256 by default. · ac398c3b
      Lasse Collin authored
      This is the sane thing to do. The conflict with OpenSSL
      on some OSes and especially that the OS-provided versions
      can be significantly slower makes it clear that it was
      a mistake to have the external SHA-256 support enabled by
      default.
      
      Those who want it can now pass --enable-external-sha256 to
      configure. INSTALL was updated with notes about OSes where
      this can be a bad idea.
      
      The SHA-256 detection code in configure.ac had some bugs that
      could lead to a build failure in some situations. These were
      fixed, although it doesn't matter that much now that the
      external SHA-256 is disabled by default.
      
      MINIX >= 3.2.0 uses NetBSD's libc and thus has SHA256_Init
      in libc instead of libutil. Support for the libutil version
      was removed.
      ac398c3b
  18. 10 Mar, 2016 2 commits
    • Lasse Collin's avatar
      Update THANKS. · 6fd5ecb5
      Lasse Collin authored
      6fd5ecb5
    • Lasse Collin's avatar
      Build: Avoid SHA256_Init on FreeBSD and MINIX 3. · 473ef0dc
      Lasse Collin authored
      On FreeBSD 10 and older, SHA256_Init from libmd conflicts
      with libcrypto from OpenSSL. The OpenSSL version has
      different sizeof(SHA256_CTX) and it can cause weird
      problems if wrong SHA256_Init gets used.
      
      Looking at the source, MINIX 3 seems to have a similar issue but
      I'm not sure. To be safe, I disabled SHA256_Init on MINIX 3 too.
      
      NetBSD has SHA256_Init in libc and they had a similar problem,
      but they already fixed it in 2009.
      
      Thanks to Jim Wilcoxson for the bug report that helped
      in finding the problem.
      473ef0dc
  19. 08 Nov, 2015 1 commit
  20. 04 Nov, 2015 2 commits
    • Lasse Collin's avatar
      Update THANKS. · e52e9151
      Lasse Collin authored
      e52e9151
    • Lasse Collin's avatar
      liblzma: Make Valgrind happier with optimized (gcc -O2) liblzma. · 14115f84
      Lasse Collin authored
      When optimizing, GCC can reorder code so that an uninitialized
      value gets used in a comparison, which makes Valgrind unhappy.
      It doesn't happen when compiled with -O0, which I tend to use
      when running Valgrind.
      
      Thanks to Rich Prohaska. I remember this being mentioned long
      ago by someone else but nothing was done back then.
      14115f84
  21. 03 Nov, 2015 2 commits