about summary refs log tree commit diff
path: root/pkgs/os-specific/linux/bpftrace
AgeCommit message (Collapse)AuthorFilesLines
2019-12-04linuxPackages.bpftrace: 0.9.2 -> 0.9.3R. RyanTM1-2/+2
2019-10-14linuxPackages.bpftrace: 0.9.1 -> 0.9.2Austin Seipp1-2/+2
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-08-15treewide: name -> pname (easy cases) (#66585)volth1-1/+1
treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
2019-07-17linuxPackages.bpftrace: 0.9 -> 0.9.1Austin Seipp2-6/+6
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-03bpftrace: nuke some unneeded files from $outAustin Seipp1-0/+6
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-03bpftrace: unstable-2018-10-27 -> 0.9Austin Seipp4-141/+56
Update bpftrace to the latest pre-release, with a real version number. The most notable change now is that bpftrace can use a stable version of the 'bcc' toolchain in order to build, meaning no more hacks are needed to clone the source code and fix up the build system, etc. This simplifies things greatly and removes the old bcc-source patch. Similarly, we can remove our custom gtests patch (which disabled the build) by just passing -DBUILD_TESTING=FALSE when running cmake. This was also added upstream recently. However, something does still need to be fixed, at a cost: bpftrace requires the kernel -dev package because it wants both objects and include directories (some files are only shipped in one or the other). Therefore, we remove the dependency on linuxHeaders and instead use kernel.dev as the sole input to the build. This is both a positive and a negative: the positive is that tools work without annoying fatal errors, and that the bpf toolchain is synchronized to the linuxPackages.kernel derivation it was built against. The downside is that the .dev expression is much heavier as a dependency, so bpftrace is now closer to 700mb in closure size. (This especially hurts across kernel upgrades requiring a whole new rebuild, especially if you have existing nixos generations that won't GC, etc.) We probably want to slim this down substantially in the future (and there may be a few ways to do that), but as this will probably also touch bcc, and as a first cut of the pre-releases, this is probably fine while we work out other kinks. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2018-10-28linuxPackages.bpftrace: init at unstable-2018-10-27Rodney Lorrimar3-0/+162