summary refs log tree commit diff
path: root/pkgs/os-specific/linux/bpftrace
Commit message (Collapse)AuthorAge
* bpftrace: 0.19.0 -> 0.19.1R. Ryantm2023-10-07
|
* bpftrace: 0.18.1 -> 0.19.0Dominique Martinet2023-09-19
| | | | | | | | | - update version - make symlinks relative directly (default postInstall was fixing links anyway, this just makes it so they are correct without fix) - fix shebang on scripts (use store path instead of /usr/bin/env) For some reason patchShebangs didn't work here (should be done automatically in post install fixups as well), use sed directly.
* bpftrace: 0.18.0 -> 0.18.1Muhammad Falak R Wani2023-09-06
| | | | | Changelog: https://github.com/iovisor/bpftrace/releases/tag/v0.18.1 Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
* bpftrace: add mfrw as maintainerMuhammad Falak R Wani2023-09-06
| | | | Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
* bpftrace: 0.17.1 -> 0.18.0Dominique Martinet2023-05-19
| | | | | | - Add patch to fix build - While we're here uniformize style a bit, so there's lot of fluff, but it's really just version bump + patch...
* bpftrace: 0.17.0 -> 0.17.1R. Ryantm2023-04-25
|
* bpftrace: 0.16.0 -> 0.17.0Masanori Misono2023-02-03
|
* bpftrace: 0.15.0 -> 0.16.0Dominique Martinet2022-12-01
| | | | | note bcc 0.25.0 breaks bpftrace 0.15.0, so this needs to be together with bcc upgrade
* bpftrace: pull upstream fix for binutils-2.39Sergei Trofimovich2022-08-25
| | | | | | | | Without the change build fails on binutils-2.39 branch as: jit_disasm.c:105:17: error: too few arguments to function 'init_disassemble_info' 105 | init_disassemble_info(&info, stdout, | ^~~~~~~~~~~~~~~~~~~~~
* bpftrace: remove libelf extraneous dependencyDominique Martinet2022-07-13
| | | | elfutils provides a libelf, we don't need it twice
* Merge #175467: libbpf 0.7.0 -> 0.8.0, bpftrace: 0.14.1 -> 0.15.0Vladimír Čunát2022-07-09
|\
| * bpftrace: 0.14.1 -> 0.15.0Dominique Martinet2022-06-10
| |
* | bpftrace: Pull tools into PATHKlemens Nanni2022-06-23
|/ | | | | | | | | | | | | | The *.bt(8) tools are meant to be used as standalone scripts, their synopsis demonstrates this usage. Especially under NixOS, calling them via their absoloute path in interactive shells is a huge pain, however. Symlink them next to bpftrace(8) itself so they end up in `PATH` but do not move them to avoid breaking existing setups that expect them under share/tools/. This goes in line with our bcc as well as Debian's bpftrace package.
* bpftrace: Rename *.8 to *.bt.8 to avoid bcc conflictsKlemens Nanni2022-05-30
| | | | | | | | | | | | | bpftrace ships *.bt replacement scripts for the original bcc programs but still installs their manual pages as *.8 rather than *.bt.8 which conflicts with the original manual pages. Rename them to recover the original manuals and avoid conflict spam: ``` building '/nix/store/jspx13hyfi2m9vlnbj5iywk6rxpxp7y0-system-path.drv'... warning: collision between `/nix/store/dv7x07rmd2m7596f38kl9d5bnv545qz7-bpftrace-0.14.1-man/share/man/man8/biolatency.8.gz' and `/nix/store/lw1kw7077wk3j6cnvjrm904rs2w7785p-bcc-0.24.0/share/man/man8/biolatency.8.gz' [... 28 more duplicate manuals ...] ```
* bpftrace: 0.14.0 -> 0.14.1R. Ryantm2022-01-12
|
* bpftrace: fix build with libbpf 0.6.0Dominique Martinet2021-12-06
| | | | | | libbpf 0.6.0 relies on typeof in bpf/btf.h to pick the right version of btf_dump__new() but that's not valid c++. see https://github.com/iovisor/bpftrace/issues/2068
* nixos/tests: add bpf testDominique Martinet2021-12-04
| | | | test bcc and bpftrace briefly
* bpftrace: 0.13.0 -> 0.14.0Dominique Martinet2021-12-04
|
* bpftrace: move from linux kernel packages to normal packageDominique Martinet2021-12-04
| | | | | | | bpftrace doesn't actually need to be a kernel package anymore. It used to require path to kernel sources, but we build our kernels with IKHEADER and BTF so the currently running configuration can always be found automatically without any patch
* 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
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-07 00:59:15 +0000