After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 140932 - Problem testing gstreamer 0.8.1
Problem testing gstreamer 0.8.1
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.8.1
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-23 13:29 UTC by Pierre
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pierre 2004-04-23 13:29:45 UTC 
[...]
Making check in manual
gmake[2]: Entering directory `/tmp/gstreamer-0.8.1/docs/manual'
gmake  check-local
gmake[3]: Entering directory `/tmp/gstreamer-0.8.1/docs/manual'
/bin/sh: -c: line 1: syntax error near unexpected token `;'
/bin/sh: -c: line 1: `if test "x" != "x"; then for a in ; do cp ./$a build;
done; fi'
gmake[3]: *** [build/manual.xml] Error 2
gmake[3]: Leaving directory `/tmp/gstreamer-0.8.1/docs/manual'
gmake[2]: *** [check-am] Error 2
gmake[2]: Leaving directory `/tmp/gstreamer-0.8.1/docs/manual'
gmake[1]: *** [check-recursive] Error 1
gmake[1]: Leaving directory `/tmp/gstreamer-0.8.1/docs'
gmake: *** [check-recursive] Error 1
Comment 1 Benjamin Otte (Company) 2004-04-25 12:11:50 UTC 
You don't use bash as your shell, right?
Comment 2 Pierre 2004-04-26 05:18:22 UTC 
Wrong, I'm using bash.
Comment 3 David Schleef 2004-04-26 19:08:57 UTC 
This is a bug in bash that affects (at least) the RPM in Mandrake 9.2.  I'd
recommend either changing to a non-buggy version of bash, using a different
shell (such as dash) for /bin/sh, or not building the documentation.
Comment 4 Pierre 2004-04-29 01:06:41 UTC 
I have the latest bash (2.05b).
Have you any reference about this bug ?
Comment 6 Pierre 2004-04-29 02:32:43 UTC 
This is a bug that was fixed in 2.05a, and I have 2.05b :

# bash --version
GNU bash, version 2.05b.0(1)-release (i686-pc-linux-gnu)
Copyright (C) 2002 Free Software Foundation, Inc.

Are you sure it is this one ?
Comment 7 Ronald Bultje 2004-04-29 12:01:51 UTC 
This patch was not part of the upstream release. Where did you read that it was
fixed in 2.05b?
Comment 8 Pierre 2004-04-30 17:55:37 UTC 
Sorry I probably misunderstand.
I will try to deal this issue with the bash team.
Comment 9 Pierre 2004-05-01 21:39:49 UTC 
Ok I finally solved this, I had 2 bash in PATH and wasn't using the new one.
But I can confirm that this issue was fixed in 2.05a.