Bug 57018

Summary: syntax error near unexpected token `[2.4.2]'
Product: Mesa Reporter: Minghui Lu <shirley4701>
Component: OtherAssignee: mesa-dev
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium    
Version: 9.0   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Minghui Lu 2012-11-12 15:34:58 UTC
Hello,

I try to install Mesa
When I do ./configure
then it gives the error

./configure: line 4522: syntax error near unexpected token `[2.4.2]'
./configure: line 4522: `LT_PREREQ([2.4.2])'

I checked goole, most of them said it's the problem of the version of my libtool
So I updated the libtool to 2.4.2 (the lastest version)
but it still gives the same problem.
Comment 1 Matt Turner 2013-01-23 02:21:21 UTC
This looks similar to https://bugs.freedesktop.org/show_bug.cgi?id=37117 (a bug for libdrm) but I don't know what the problem is.
Comment 2 Andreas Boll 2013-02-27 10:09:22 UTC
Does this happen if you build from git or from release tarball?
Comment 3 Antonio Alecrim Jr 2013-09-21 00:25:52 UTC
git sha1: 1569b3e536da9337a28a16d0cc6ed07043bf094b

To reproduce this "bug":
mesa> ./autogen.sh
...
src/egl/drivers/dri2/Makefile.am:37: error: Libtool library used but 'LIBTOOL' is undefined
...
autoreconf: automake failed with exit status: 1
mesa> ./configure
...
./configure: line 5129: syntax error near unexpected token `2.2'
./configure: line 5129: `LT_PREREQ(2.2)'

To fix this "bug" I commented these problematic lines and installed all required packages.
To fix "autogen.sh" error I installed "Libtool":
> git clean -xfd
> ./autogen.sh
> ./configure

And everything works fine.
Maybe is just an environment problem.

Can you check if this solves your problem?
Comment 4 themastir 2014-05-13 09:42:52 UTC
i got the same error messages on ubuntu 14.04. The solution for me was to install libtool package via apt.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.