summary refs log tree commit diff
path: root/pkgs/os-specific/linux/bpftrace
Commit message (Collapse)AuthorAge
* linuxPackages_5_4.bpftrace: 0.12.1 -> 0.13.0R. RyanTM2021-07-03
|
* linuxPackages.bpftrace: 0.12.0 -> 0.12.1R. RyanTM2021-05-17
|
* linuxPackages.bpftrace: fix llvm buildJonathan Ringer2021-05-08
|
* linuxPackages.bpftrace: 0.11.4 -> 0.12.0V2021-04-02
|
* treewide: pkgs.pkgconfig -> pkgs.pkg-config, move pkgconfig to alias.nixJonathan Ringer2021-01-19
| | | | | | | | | | | | | continuation of #109595 pkgconfig was aliased in 2018, however, it remained in all-packages.nix due to its wide usage. This cleans up the remaining references to pkgs.pkgsconfig and moves the entry to aliases.nix. python3Packages.pkgconfig remained unchanged because it's the canonical name of the upstream package on pypi.
* pkgs/os-specific: stdenv.lib -> libBen Siraphob2021-01-17
|
* treewide: with stdenv.lib; in meta -> with lib;Profpatsch2021-01-11
| | | | | | | | | | | | | | | | | | | Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
* treewide: remove enableParallelBuilding = true if using cmakeBen Siraphob2021-01-03
|
* linuxPackages.bpftrace: 0.11.0 -> 0.11.4Sarah Brofeldt2020-11-28
|
* linuxPackages.bpftrace: 0.9.4 -> 0.11.0Austin Seipp2020-08-31
| | | | | | | | This fixes the `bcc` include directory (which was improperly set, and warned about at build-time, but masked by some backwards compat code, apparently) and also includes some missing libraries in `buildInputs` Signed-off-by: Austin Seipp <aseipp@pobox.com>
* linuxPackages.bpftrace: 0.9.3 -> 0.9.4Maximilian Bosch2020-04-13
| | | | https://github.com/iovisor/bpftrace/releases/tag/v0.9.4
* treewide: Per RFC45, remove all unquoted URLsMichael Reilly2020-04-10
|
* linuxPackages.bpftrace: 0.9.2 -> 0.9.3R. RyanTM2019-12-04
|
* linuxPackages.bpftrace: 0.9.1 -> 0.9.2Austin Seipp2019-10-14
| | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
* treewide: name -> pname (easy cases) (#66585)volth2019-08-15
| | | | | | | | | treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
* linuxPackages.bpftrace: 0.9 -> 0.9.1Austin Seipp2019-07-17
| | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
* bpftrace: nuke some unneeded files from $outAustin Seipp2019-05-03
| | | | Signed-off-by: Austin Seipp <aseipp@pobox.com>
* bpftrace: unstable-2018-10-27 -> 0.9Austin Seipp2019-05-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* linuxPackages.bpftrace: init at unstable-2018-10-27Rodney Lorrimar2018-10-28