Nixpkgs: bitlbee does not build

Created on 19 Nov 2019  路  1Comment  路  Source: NixOS/nixpkgs

Describe the bug
Bitlbee does not build on master.

To Reproduce
Steps to reproduce the behavior:

  1. nix-build --no-build-output -A bitlbee
these derivations will be built:
  /nix/store/2a69lfr8r6zh6d20nwvqyxcd6p9yii05-bitlbee-3.6.drv
building '/nix/store/2a69lfr8r6zh6d20nwvqyxcd6p9yii05-bitlbee-3.6.drv'...
builder for '/nix/store/2a69lfr8r6zh6d20nwvqyxcd6p9yii05-bitlbee-3.6.drv' failed with exit code 2; last 10 log lines:
              ^~~~~~~~~~~~~~~~~
  check_util.c:27:12: warning: 'test_strip_newlines' defined but not used [-Wunused-variable]
   START_TEST(test_strip_newlines)
              ^~~~~~~~~~~~~~~~~~~
  check_util.c:11:12: warning: 'test_strip_linefeed' defined but not used [-Wunused-variable]
   START_TEST(test_strip_linefeed){
              ^~~~~~~~~~~~~~~~~~~
  make[1]: *** [Makefile:27: check_util.o] Error 1
  make[1]: Leaving directory '/build/bitlbee-3.6/tests'
  make: *** [Makefile:65: check] Error 2
error: build of '/nix/store/2a69lfr8r6zh6d20nwvqyxcd6p9yii05-bitlbee-3.6.drv' failed

Expected behavior
The bitlbee derivation should build without errors.

Metadata

  • system: "x86_64-linux"
  • host os: Linux 5.3.11, NixOS, 20.03.git.6be20178f08 (Markhor)
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.3.1
  • nixpkgs: 25fc378642e

Maintainer information:

attribute:
- bitlbee
- bitlbee-steam
- bitlbee-mastodon
- bitlbee-facebook
- bitlbee-discord
# a list of nixos modules affected by the problem
module:
- services/networking/bitlbee

@pSub

bug

Most helpful comment

Bisecting pointed me to the following commit. It seems like START_TEST changed a bit and use without creating a block to contain the unit-test code stopped working.

738fdb49830feb3e0594c053970b1e08ab45ffb1 is the first bad commit
commit 738fdb49830feb3e0594c053970b1e08ab45ffb1
Author: R. RyanTM <[email protected]>
Date:   Fri Nov 1 12:33:14 2019 -0700

    check: 0.12.0 -> 0.13.0

Looks like it was done in this commit in libcheck: https://github.com/libcheck/check/commit/3987c1d906ee68e0a6a5fd7888d88e0873f914d9

>All comments

Bisecting pointed me to the following commit. It seems like START_TEST changed a bit and use without creating a block to contain the unit-test code stopped working.

738fdb49830feb3e0594c053970b1e08ab45ffb1 is the first bad commit
commit 738fdb49830feb3e0594c053970b1e08ab45ffb1
Author: R. RyanTM <[email protected]>
Date:   Fri Nov 1 12:33:14 2019 -0700

    check: 0.12.0 -> 0.13.0

Looks like it was done in this commit in libcheck: https://github.com/libcheck/check/commit/3987c1d906ee68e0a6a5fd7888d88e0873f914d9

Was this page helpful?
0 / 5 - 0 ratings