Steps To Reproduce
Steps to reproduce the behavior:
- build
prusa-slicer with current master
Build log
build log on hydra
Additional context
I did a git bisect --first-parent and found #183748 (with commit a0ebaa7) to be the first bad commit. Looking through the commits on that staging-next run, I tried reverting e682dd8 and could build prusa-slicer again.
So it seems to be a regression caused in binutils-wrapper
Notify maintainers
@Artturin (author of commit)
@vcunat (staging-next run)
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
- host os: `Linux 5.15.56, NixOS, 22.11 (Raccoon), 22.11.20220729.99d2206`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.10.3`
- channels(root): `"nixos, nixpkgs"`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
Steps To Reproduce
Steps to reproduce the behavior:
prusa-slicerwith current masterBuild log
build log on hydra
Additional context
I did a
git bisect --first-parentand found #183748 (with commit a0ebaa7) to be the first bad commit. Looking through the commits on that staging-next run, I tried reverting e682dd8 and could build prusa-slicer again.So it seems to be a regression caused in
binutils-wrapperNotify maintainers
@Artturin (author of commit)
@vcunat (staging-next run)
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"and paste the result.