'guix-build' returns 'unknown package', Bison's testsuite fails

unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed

* 'guix-build' returns 'unknown package', Bison's testsuite fails
@ 2013-01-26 13:10 Nikita Karetnikov
  2013-01-26 17:21 ` Andreas Enge
  2013-01-26 21:03 ` Ludovic Courtès
  0 siblings, 2 replies; 6+ messages in thread
From: Nikita Karetnikov @ 2013-01-26 13:10 UTC (permalink / raw)
  To: bug-guix

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hi,

I'm trying to package 'gobject-introspection', but I'm facing some
problems:

  1. 'guix-build' doesn't work for new packages; it returns
     "<package>: unknown package."  I'm using the '-e' option as a
     workaround, but it's not very convenient.

     For instance, if I copy the recipe for 'sed' to 'newsed.scm', then
     replace 'sed' with 'newsed' in that file, and try to build it via
     'guix-build newsed', it will return the mentioned error message.
     However, it will work if I use the '-e' option.  Also, I won't get
     any errors if I try to import it in the REPL.

  2. Bison's testsuite fails and I'm not able to fix it.  So I'd like to
     disable it because I want to test 'gobject-introspection'.  Why
     doesn't '(arguments `(#:tests? #f))' disable the testsuite?

These issues may seem unrelated, but there is a similarity: My changes
have no effect.  I've just replaced 'gnu/packages/bison.scm' with an
empty file, but 'guix-build bison' doesn't raise any errors.  Is it
related?

Nikita

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 'guix-build' returns 'unknown package', Bison's testsuite fails
  2013-01-26 13:10 'guix-build' returns 'unknown package', Bison's testsuite fails Nikita Karetnikov
@ 2013-01-26 17:21 ` Andreas Enge
  2013-01-26 21:03 ` Ludovic Courtès
  1 sibling, 0 replies; 6+ messages in thread
From: Andreas Enge @ 2013-01-26 17:21 UTC (permalink / raw)
  To: bug-guix

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

Am Samstag, 26. Januar 2013 schrieb Nikita Karetnikov:
> I'm trying to package 'gobject-introspection', but I'm facing some
> problems:
>   1. 'guix-build' doesn't work for new packages; it returns
>      "<package>: unknown package."  I'm using the '-e' option as a
>      workaround, but it's not very convenient.
> 
>      For instance, if I copy the recipe for 'sed' to 'newsed.scm', then
>      replace 'sed' with 'newsed' in that file, and try to build it via
>      'guix-build newsed', it will return the mentioned error message.
>      However, it will work if I use the '-e' option.  Also, I won't get
>      any errors if I try to import it in the REPL.
> 
>   2. Bison's testsuite fails and I'm not able to fix it.  So I'd like to
>      disable it because I want to test 'gobject-introspection'.  Why
>      doesn't '(arguments `(#:tests? #f))' disable the testsuite?
> 
> These issues may seem unrelated, but there is a similarity: My changes
> have no effect.  I've just replaced 'gnu/packages/bison.scm' with an
> empty file, but 'guix-build bison' doesn't raise any errors.  Is it
> related?

That has happened to me before when I forgot to execute "make install" or 
to add a file to Makefile.am.

Also, after deleting a file, it is not deleted from $PREFIX/share/...; in 
this way, it has happened to me that I had two versions of a package, one 
from a deleted/renamed file, one from the file with the new name; and the 
wrong one was built...

Andreas

[-- Attachment #2: Type: text/html, Size: 5888 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 'guix-build' returns 'unknown package', Bison's testsuite fails
  2013-01-26 13:10 'guix-build' returns 'unknown package', Bison's testsuite fails Nikita Karetnikov
  2013-01-26 17:21 ` Andreas Enge
@ 2013-01-26 21:03 ` Ludovic Courtès
  2013-01-28 14:35   ` Bison: testsuite failed (was: 'guix-build' returns 'unknown package', Bison's testsuite fails) Nikita Karetnikov
  1 sibling, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2013-01-26 21:03 UTC (permalink / raw)
  To: Nikita Karetnikov; +Cc: bug-guix

Hi,

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>   1. 'guix-build' doesn't work for new packages; it returns
>      "<package>: unknown package."  I'm using the '-e' option as a
>      workaround, but it's not very convenient.

‘guix-build’ searches all modules under gnu/packages; in those modules,
it searches all the public variables that match ‘package?’, and finally
compares against their ‘name’ field.

Could it be that your package is not in a public variable?

>      For instance, if I copy the recipe for 'sed' to 'newsed.scm', then
>      replace 'sed' with 'newsed' in that file, and try to build it via
>      'guix-build newsed', it will return the mentioned error message.

That’s expected: what matters it the ‘name’ field of the ‘<package>’
instance, not the name of the file that defines it.

>   2. Bison's testsuite fails and I'm not able to fix it.  So I'd like to
>      disable it because I want to test 'gobject-introspection'.  Why
>      doesn't '(arguments `(#:tests? #f))' disable the testsuite?

Can you provide more details?  It appears to build for me as
/nix/store/2kdr905aj5kkm0mrwjqxsgv6zvmh2y0j-bison-2.6.1 (x86_64-linux).

> These issues may seem unrelated, but there is a similarity: My changes
> have no effect.  I've just replaced 'gnu/packages/bison.scm' with an
> empty file, but 'guix-build bison' doesn't raise any errors.  Is it
> related?

Actually, there’s an evil bug.  ‘guix-build’ & co. do this:

  GUILE_LOAD_COMPILED_PATH="@guilemoduledir@:$GUILE_LOAD_COMPILED_PATH"
  export GUILE_LOAD_COMPILED_PATH

So if you’ve run ‘make install’ before, the installed modules will
prevail over the non-installed ones.

I’ll see how to fix it.  In the meantime, you can, ahem, run
‘make uninstall’ or ‘make install’...

Thanks,
Ludo’.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Bison: testsuite failed (was: 'guix-build' returns 'unknown package', Bison's testsuite fails)
  2013-01-26 21:03 ` Ludovic Courtès
@ 2013-01-28 14:35   ` Nikita Karetnikov
  2013-01-28 16:35     ` Bison: testsuite failed Ludovic Courtès
  0 siblings, 1 reply; 6+ messages in thread
From: Nikita Karetnikov @ 2013-01-28 14:35 UTC (permalink / raw)
  To: Ludovic Courtès; +Cc: bug-guix


[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]

> I’ll see how to fix it.  In the meantime, you can, ahem, run
> ‘make uninstall’ or ‘make install’...

I'm not sure, but I think that 'make uninstall' solved the problem.

> Can you provide more details?  It appears to build for me as
> /nix/store/2kdr905aj5kkm0mrwjqxsgv6zvmh2y0j-bison-2.6.1 (x86_64-linux).

I've attached the part of 'testsuite.log'.

Nikita


[-- Attachment #1.2: bison-testsuite.log --]
[-- Type: text/plain, Size: 14551 bytes --]

## ------------- ##
## Test results. ##
## ------------- ##

ERROR: 303 tests were run,
14 failed unexpectedly.
18 tests were skipped.

## ------------------------ ##
## Summary of the failures. ##
## ------------------------ ##
Failed tests:
GNU Bison 2.6.1 test suite test groups:

 NUM: FILE-NAME:LINE     TEST-GROUP-NAME
      KEYWORDS

  22: input.at:828       Reject unused %code qualifiers
  23: input.at:917       %define errors
  24: input.at:953       %define, --define, --force-define
  25: input.at:1006      %define Boolean variables
  26: input.at:1026      %define enum variables
  27: input.at:1060      %define backward compatibility
  28: input.at:1101      Unused %define api.pure
  29: input.at:1134      C++ namespace reference errors
  32: input.at:1292      LAC: Errors for %define
  34: input.at:1349      %name-prefix and %define api.prefix are incompatible
  86: skeletons.at:146   %define Boolean variables: invalid skeleton defaults
  87: skeletons.at:170   Complaining during macro argument expansion
  88: skeletons.at:252   Fatal errors make M4 exit immediately
 321: push.at:144        Unsupported Skeletons

[...]

## ---------------------- ##
## Detailed failed tests. ##
## ---------------------- ##

#                             -*- compilation -*-
22. input.at:828: testing Reject unused %code qualifiers ...
./input.at:838: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input-c.y
--- -	2013-01-28 12:46:55.161389523 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/22/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,5 +1,4 @@
-input-c.y:1.7: %code qualifier 'q' is not used
-input-c.y:2.7-9: %code qualifier 'bad' is not used
-input-c.y:3.7-9: %code qualifier 'bad' is not used
-input-c.y:4.7-12: %code qualifier 'format' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./input.at:838: exit code was 0, expected 1
22. input.at:828: 22. Reject unused %code qualifiers (input.at:828): FAILED (input.at:838)

#                             -*- compilation -*-
23. input.at:917: testing %define errors ...
./input.at:929: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input-redefined.y
./input.at:942: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input-unused.y
--- -	2013-01-28 12:46:55.197652853 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/23/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-input-unused.y:1.9-11: %define variable 'var' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./input.at:942: exit code was 0, expected 1
23. input.at:917: 23. %define errors (input.at:917): FAILED (input.at:942)

#                             -*- compilation -*-
24. input.at:953: testing %define, --define, --force-define ...
./input.at:969: bison -Dvar-dd=cmd-d1 -Dvar-dd=cmd-d2 \
                 -Fvar-ff=cmd-f1 -Fvar-ff=cmd-f2 \
                 -Dvar-dfg=cmd-d -Fvar-dfg=cmd-f \
                 -Fvar-fd=cmd-f -Dvar-fd=cmd-d   \
                 --skeleton ./skel.c input.y
./input.at:974: cat input.tab.c
./input.at:986: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison -Dvar=cmd-d input-dg.y
./input.at:995: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison -Dunused-d -Funused-f input-unused.y
--- -	2013-01-28 12:46:55.254872853 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/24/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,3 +1,4 @@
-<command line>:2: %define variable 'unused-d' is not used
-<command line>:3: %define variable 'unused-f' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./input.at:995: exit code was 0, expected 1
24. input.at:953: 24. %define, --define, --force-define (input.at:953): FAILED (input.at:995)

#                             -*- compilation -*-
25. input.at:1006: testing %define Boolean variables ...
./input.at:1016: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison Input.y
--- -	2013-01-28 12:46:55.282046571 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/25/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-Input.y:2.9-14: invalid value for %define Boolean variable 'public'
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/lalr1.java:39: error: b4_cat: cannot write to stdout
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/lalr1.java:39: the top level
 
./input.at:1016: exit code was 0, expected 1
25. input.at:1006: 25. %define Boolean variables (input.at:1006): FAILED (input.at:1016)

#                             -*- compilation -*-
26. input.at:1026: testing %define enum variables ...
./input.at:1034: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
./input.at:1047: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:46:55.308466592 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/26/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,5 +1,4 @@
-input.y:1.9-21: invalid value for %define variable 'api.push-pull': 'neither'
-input.y:1.9-21: accepted value: 'pull'
-input.y:1.9-21: accepted value: 'push'
-input.y:1.9-21: accepted value: 'both'
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: error: b4_cat: cannot write to stdout
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: the top level
 
./input.at:1047: exit code was 0, expected 1
26. input.at:1026: 26. %define enum variables (input.at:1026): FAILED (input.at:1047)

#                             -*- compilation -*-
27. input.at:1060: testing %define backward compatibility ...
./input.at:1070: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:46:55.333478769 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/27/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,5 +1,4 @@
-input.y:1.9-21: invalid value for %define variable 'api.push-pull': 'neither'
-input.y:1.9-21: accepted value: 'pull'
-input.y:1.9-21: accepted value: 'push'
-input.y:1.9-21: accepted value: 'both'
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: error: b4_cat: cannot write to stdout
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: the top level
 
./input.at:1070: exit code was 0, expected 1
27. input.at:1060: 27. %define backward compatibility (input.at:1060): FAILED (input.at:1070)

#                             -*- compilation -*-
28. input.at:1101: testing Unused %define api.pure ...
./input.at:1121: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:46:55.364713405 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/28/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-input.y:1.9-16: %define variable 'api.pure' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./input.at:1121: exit code was 0, expected 1
28. input.at:1101: 28. Unused %define api.pure (input.at:1101): FAILED (input.at:1121)

#                             -*- compilation -*-
29. input.at:1134: testing C++ namespace reference errors ...
./input.at:1155: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:46:55.389100722 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/29/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-input.y:3.9-17: namespace reference is empty
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/c++.m4:55: error: b4_cat: cannot write to stdout
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/c++.m4:55: the top level
 
./input.at:1155: exit code was 0, expected 1
29. input.at:1134: 29. C++ namespace reference errors (input.at:1134): FAILED (input.at:1155)

#                             -*- compilation -*-
32. input.at:1292: testing LAC: Errors for %define ...
./input.at:1300: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison -Dparse.lac.es-capacity-initial=1 input.y
--- -	2013-01-28 12:46:55.577889824 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/32/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-<command line>:2: %define variable 'parse.lac.es-capacity-initial' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./input.at:1300: exit code was 0, expected 1
32. input.at:1292: 32. LAC: Errors for %define (input.at:1292): FAILED (input.at:1300)

#                             -*- compilation -*-
34. input.at:1349: testing %name-prefix and %define api.prefix are incompatible ...
./input.at:1364: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison  input.y
--- -	2013-01-28 12:46:55.711101149 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/34/stderr	2013-01-28 12:46:55.000000000 +0000
@@ -1,2 +1,4 @@
-input.y:1.9-18: '%name-prefix' and '%define api.prefix' cannot be used together
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/bison.m4:581: error: b4_cat: cannot write to stdout
+/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/bison.m4:581: the top level
 
./input.at:1364: exit code was 0, expected 1
34. input.at:1349: 34. %name-prefix and %define api.prefix are incompatible (input.at:1349): FAILED (input.at:1364)

#                             -*- compilation -*-
86. skeletons.at:146: testing %define Boolean variables: invalid skeleton defaults ...
./skeletons.at:159: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:47:05.168542489 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/86/stderr	2013-01-28 12:47:05.000000000 +0000
@@ -1,2 +1,4 @@
-<skeleton default value>: invalid value for %define Boolean variable 'foo'
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+./skel.c:2: error: b4_cat: cannot write to stdout
+./skel.c:2: the top level
 
./skeletons.at:159: exit code was 0, expected 1
86. skeletons.at:146: 86. %define Boolean variables: invalid skeleton defaults (skeletons.at:146): FAILED (skeletons.at:159)

#                             -*- compilation -*-
87. skeletons.at:170: testing Complaining during macro argument expansion ...
./skeletons.at:193: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input1.y
--- -	2013-01-28 12:47:05.195636562 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/87/stderr	2013-01-28 12:47:05.000000000 +0000
@@ -1,6 +1,4 @@
-input1.y: warning: foow fubar
-foow.y:2.3-5.3: warning: foowat fubar
-input1.y: fooc fubar
-fooc.y:1.1-10.5: foocat fubar
-input1.y: fatal error: foof fubar
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+./skel1.c:8: error: b4_cat: cannot write to stdout
+./skel1.c:8: the top level
 
./skeletons.at:193: exit code was 0, expected 1
87. skeletons.at:170: 87. Complaining during macro argument expansion (skeletons.at:170): FAILED (skeletons.at:193)

#                             -*- compilation -*-
88. skeletons.at:252: testing Fatal errors make M4 exit immediately ...
./skeletons.at:266: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input1.y
--- -	2013-01-28 12:47:05.220410500 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/88/stderr	2013-01-28 12:47:05.000000000 +0000
@@ -1,3 +1,4 @@
-input1.y: non-fatal error
-input1.y: fatal error: M4 should exit immediately here
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+./skel1.c:1: error: b4_cat: cannot write to stdout
+./skel1.c:1: the top level
 
./skeletons.at:266: exit code was 0, expected 1
88. skeletons.at:252: 88. Fatal errors make M4 exit immediately (skeletons.at:252): FAILED (skeletons.at:266)

#                             -*- compilation -*-
321. push.at:144: testing Unsupported Skeletons ...
./push.at:155: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary --show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -	2013-01-28 12:48:56.976256959 +0000
+++ /tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/tests/testsuite.dir/at-groups/321/stderr	2013-01-28 12:48:56.000000000 +0000
@@ -1,2 +1,4 @@
-input.y:2.9-21: %define variable 'api.push-pull' is not used
+/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
+stdin:1: error: b4_cat: cannot write to stdout
+stdin:1: the top level
 
./push.at:155: exit code was 0, expected 1
321. push.at:144: 321. Unsupported Skeletons (push.at:144): FAILED (push.at:155)

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bison: testsuite failed
  2013-01-28 14:35   ` Bison: testsuite failed (was: 'guix-build' returns 'unknown package', Bison's testsuite fails) Nikita Karetnikov
@ 2013-01-28 16:35     ` Ludovic Courtès
  2013-01-31  5:18       ` Nikita Karetnikov
  0 siblings, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2013-01-28 16:35 UTC (permalink / raw)
  To: Nikita Karetnikov; +Cc: bug-guix

Hi,

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> +/nix/store/6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16/bin/m4: m4_syscmd subprocess failed
> +/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: error: b4_cat: cannot write to stdout
> +/tmp/nix-build-bison-2.6.1.drv-14/bison-2.6.1/data/yacc.c:23: the top level

Can you check in the build log of 6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16
what the line “checking which shell to use for syscmd” says?  (Remember
that build logs are kept in /nix/var/log/nix/drvs or similar, depending
on your localstatedir.  Make sure the value passed to --prefix in that
log matches the one above.)

Here it reads this:

  checking which shell to use for syscmd... /nix/store/ryk1ywzz31kp4biclxq3yq6hpjycalyy-bash-4.2/bin/sh

If it chose /bin/sh, then it means that you built M4 out of the chroot
(or with /bin in the chroot), but now you’re trying to use it within a
chroot.

Ludo’.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bison: testsuite failed
  2013-01-28 16:35     ` Bison: testsuite failed Ludovic Courtès
@ 2013-01-31  5:18       ` Nikita Karetnikov
  0 siblings, 0 replies; 6+ messages in thread
From: Nikita Karetnikov @ 2013-01-31  5:18 UTC (permalink / raw)
  To: Ludovic Courtès; +Cc: bug-guix

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

> Can you check in the build log of 6kj7f8kz3h5fizir8l7nrxgras2ns3ww-m4-1.4.16
> what the line “checking which shell to use for syscmd” says?  (Remember
> that build logs are kept in /nix/var/log/nix/drvs or similar, depending
> on your localstatedir.  Make sure the value passed to --prefix in that
> log matches the one above.)

There were no logs.  So I ran 'nix-store --delete 6*w-m4-1.4.16', then
reinstalled it, and 'bison' succeeded.

Nikita

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-01-31  5:18 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-26 13:10 'guix-build' returns 'unknown package', Bison's testsuite fails Nikita Karetnikov
2013-01-26 17:21 ` Andreas Enge
2013-01-26 21:03 ` Ludovic Courtès
2013-01-28 14:35   ` Bison: testsuite failed (was: 'guix-build' returns 'unknown package', Bison's testsuite fails) Nikita Karetnikov
2013-01-28 16:35     ` Bison: testsuite failed Ludovic Courtès
2013-01-31  5:18       ` Nikita Karetnikov

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).