GNOME Bugzilla – Bug 632203
make distcheck fails if required orcc version isn't present
Last modified: 2010-11-01 17:47:34 UTC
This is due to the fact that ORCC is empty when calling the following rule: $(ORCC) --test -o $@ $< Which gets evaluated to: make[2]: Entering directory `/home/bilboed/buildbot/g64~-base-full/build/tests/check' /usr/bin/mkdir -p orc/ test -o orc/adder.c ../../gst/adder/gstadderorc.orc /bin/sh: line 0: test: orc/adder.c: binary operator expected make[2]: [orc/adder.c] Error 2 (ignored) /usr/bin/mkdir -p orc/ test -o orc/audioconvert.c ../../gst/audioconvert/gstaudioconvertorc.orc /bin/sh: line 0: test: orc/audioconvert.c: binary operator expected make[2]: [orc/audioconvert.c] Error 2 (ignored) /usr/bin/mkdir -p orc/ test -o orc/videoscale.c ../../gst/videoscale/gstvideoscaleorc.orc /bin/sh: line 0: test: orc/videoscale.c: binary operator expected make[2]: [orc/videoscale.c] Error 2 (ignored) /usr/bin/mkdir -p orc/ test -o orc/videotestsrc.c ../../gst/videotestsrc/gstvideotestsrcorc.orc /bin/sh: line 0: test: orc/videotestsrc.c: binary operator expected make[2]: [orc/videotestsrc.c] Error 2 (ignored) /usr/bin/mkdir -p orc/ test -o orc/volume.c ../../gst/volume/gstvolumeorc.orc /bin/sh: line 0: test: orc/volume.c: binary operator expected make[2]: [orc/volume.c] Error 2 (ignored) cp: cannot stat `./orc/adder.c': No such file or directory make[2]: *** [distdir] Error 1 make[2]: Leaving directory `/home/bilboed/buildbot/g64~-base-full/build/tests/check' make[1]: *** [distdir] Error 1 make[1]: Leaving directory `/home/bilboed/buildbot/g64~-base-full/build/tests' make: *** [distdir] Error 1 program finished with exit code 2 elapsedTime=8.756139
Should be fixed by this in common: commit 7bbd708e42adb484cb036b913403c9b8f64e55b6 Author: David Schleef <ds@schleef.org> Date: Thu Oct 14 12:25:27 2010 -0700 orc.m4: Don't set HAVE_ORCC if orc is disabled
Should... but isn't. See the f13 buildslave report (it only has orc 0.4.9 iirc) http://build.gstreamer.org:8010/builders/f13-64-base-full/builds/1054
'make dist' should fail if ORCC is unavailable. Of course, cryptic unplanned failures are less than optimal.
Can you do a 'grep ORC config.log' on the autobuilder?
[bilboed@f13buildslave build]$ grep ORC config.log configure:22282: checking for ORC configure:22290: $PKG_CONFIG --exists --print-errors "orc-0.4 >= $ORC_REQ" configure:22308: $PKG_CONFIG --exists --print-errors "orc-0.4 >= $ORC_REQ" | #define DISABLE_ORC 1 | #define DISABLE_ORC 1 | #define DISABLE_ORC 1 | #define DISABLE_ORC 1 ac_cv_env_ORC_CFLAGS_set= ac_cv_env_ORC_CFLAGS_value= ac_cv_env_ORC_LIBS_set= ac_cv_env_ORC_LIBS_value= HAVE_ORCC_FALSE='' HAVE_ORCC_TRUE='#' HAVE_ORC_FALSE='' HAVE_ORC_TRUE='#' ORCC='' ORCC_FLAGS='' ORC_CFLAGS='' ORC_LIBS='' #define DISABLE_ORC 1
commit 24582f3807fcaa9b0d9556d0e08d86f3ff53b873 Author: David Schleef <ds@schleef.org> Date: Fri Oct 15 11:23:02 2010 -0700 tests: Don't dist generated orc code