Commit graph

15 commits

Author SHA1 Message Date
Mark Vainomaa 89400633b9
mimalloc: revert doCheck enable
For some reason, test fails with binary not being able to find
libmimalloc.so.2.0. Manually specifying LD_LIBRARY_PATH gets it working,
which does not look like a very viable fix.
2021-06-29 04:30:57 +03:00
Mark Vainomaa 58e6fa615a
mimalloc: make use of MI_INSTALL_TOPLEVEL
Fixes:
- Gross file moving in postInstall (maintenance burden)
- Usability of CMake files

Also enables check phase
2021-06-29 04:30:44 +03:00
Mark Vainomaa 13034ba77a
mimalloc: 2.0.0 -> 2.0.2 2021-06-29 03:44:03 +03:00
R. RyanTM 87b5c57480 mimalloc: 1.6.7 -> 2.0.0 2021-03-20 23:46:46 -07:00
Ben Siraphob 66e44425c6 pkgs/development/libraries: stdenv.lib -> lib 2021-01-21 19:11:02 -08:00
Ben Siraphob 3ae5e6ce03 treewide: remove enableParallelBuilding = true if using cmake 2021-01-03 18:37:40 +07:00
R. RyanTM a492b32c3a mimalloc: 1.6.4 -> 1.6.7 2020-11-03 21:41:21 -08:00
R. RyanTM 66c2d629f1 mimalloc: 1.6.3 -> 1.6.4 2020-08-26 19:02:44 +00:00
R. RyanTM a31a269cb9 mimalloc: 1.6.1 -> 1.6.3 2020-05-27 12:10:28 -07:00
ajs124 194f3aa4b5 mimalloc: 1.1.0 -> 1.6.1 2020-02-19 10:31:25 -06:00
Austin Seipp 3c5767335e
mimalloc: fix one final time
The library link name is embedded in the ELF executable, so renaming the
file doesn't work. This patch just bites the bullet and writes two
separate code paths for the secure vs non-secure build...

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-12-06 18:17:27 -06:00
Austin Seipp a2f9bcd132
mimalloc: (really) unbreak dynamic linking
4d392099 didn't quite do the trick, but this should finally fix
everything -- namely, the -secure.so symlink was broken, and
libmimalloc.so itself was also a symlink that needed to be replaced with
the real shared object file.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-12-04 16:25:30 -06:00
Austin Seipp 4d39209961
mimalloc: un-break dynamic linking
Previous versions of the build assumed libmimalloc.so would be a hard
copy of mimalloc-secure.so iff secureBuild == true, but in 1.1.0 and
later it seems libmimalloc.so is a symlink to the -secure variant. This
apparently rectifies some behavior I noticed that was strange
previously.

This breakage wasn't caught because the 1.1.0 update was automatic in
5596317d4; there should be a checkPhase to ensure this doesn't happen
again...

Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-12-03 13:50:14 -06:00
R. RyanTM 5596317d42 mimalloc: 1.0.8 -> 1.1.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/mimalloc/versions
2019-10-22 17:35:47 -07:00
Austin Seipp 544b85a49a mimalloc: init at 1.0.8
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-09-23 18:10:57 -05:00