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 591310 - Configure doesn't work on Ubuntu 8.04
Configure doesn't work on Ubuntu 8.04
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.24
Other All
: Normal minor
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 591311 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-10 10:54 UTC by Miguel Angel Cabrera Moya
Modified: 2009-08-18 09:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
The configure script generated by autoconf (801.77 KB, text/plain)
2009-08-17 18:33 UTC, Miguel Angel Cabrera Moya
Details

Description Miguel Angel Cabrera Moya 2009-08-10 10:54:46 UTC
Please describe the problem:
i run configure script but i get the error

 ./configure: line 24732: syntax error near unexpected token `('
 ./configure: line 24732: `  for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do'
   configure failed

Running autogen.sh gives the same error.

Steps to reproduce:
1. run configure script
2. 
3. 

Actual results:
I get the error

./configure: line 24732: syntax error near unexpected token `('
 ./configure: line 24732: `  for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do'
   configure failed

Expected results:
configure generates Makefiles

Does this happen every time?
yes

Other information:
Comment 1 Tim-Philipp Müller 2009-08-10 11:09:44 UTC
*** Bug 591311 has been marked as a duplicate of this bug. ***
Comment 2 Sebastian Dröge (slomo) 2009-08-17 15:55:02 UTC
Do you use a tarball release of GStreamer? Which version?

If not, could you attach the configure script that is generated by autoconf to this bug? Line 24732 of configure from gstreamer 0.10.24 is a different one than the one mentioned in the original bugreport. You might need to use a newer autoconf.


Also, what's the output of
/bin/sh --version
Comment 3 Miguel Angel Cabrera Moya 2009-08-17 18:32:51 UTC
I use tarball http://gstreamer.freedesktop.org/src/gstreamer/gstreamer-0.10.24.tar.bz2

my build tools are
+ check for build tools
  checking for autoconf >= 2.52 ... found 2.61, ok.
  checking for automake >= 1.7 ... found 1.9.6, ok.
  checking for autopoint >= 0.17 ... found 0.17, ok.
  checking for libtoolize >= 1.5.0 ... found 1.5.26, ok.
  checking for pkg-config >= 0.8.0 ... found 0.22, ok.

I cannot get the version of /bin/sh because i have not found the option to do it or to display the help with available options.
Comment 4 Miguel Angel Cabrera Moya 2009-08-17 18:33:54 UTC
Created attachment 140988 [details]
The configure script generated by autoconf
Comment 5 David Schleef 2009-08-17 19:50:16 UTC
"Works for me"

Make sure that your /bin/sh is either bash or dash.
Comment 6 Miguel Angel Cabrera Moya 2009-08-17 20:41:01 UTC
My /bin/sh is a symbolic link to dash.
Comment 7 Sebastian Dröge (slomo) 2009-08-18 06:28:28 UTC
This is an autoconf bug I guess. The lines that don't work for you are from autoconf's configure check cache mechanism. You should probably file this bug again against autoconf.


Apart from that, does everything work if you use the configure script from the tarball instead of generating your own?
Comment 8 Miguel Angel Cabrera Moya 2009-08-18 09:44:19 UTC
With the configure that is packaged with the tarball i get the error

./configure: line 25368: syntax error near unexpected token `('
./configure: line 25368: `  for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do'