[Mesa-users] Building mesa 9.2rc1 fails on Fedora-19

[Ken Moffat]

On Thu, Aug 22, 2013 at 09:36:43AM +0200, Clemens Eisserer wrote:
> Hi,
> 
> When compiling 9.2rc1 after a successful configure, I run into the
> following issue on Fedora19+updates-testing:
> 
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
> /home/ce/Mesa-9.2.0-rc1/bin/missing --run aclocal-1.12 -I m4
> /home/ce/Mesa-9.2.0-rc1/bin/missing: line 51: aclocal-1.12: command not
> found
> WARNING: 'aclocal-1.12' is missing on your system.  You should only need it
> if
>          you modified 'acinclude.m4' or 'configure.ac'.  You might want
>          to install the Automake and Perl packages.  Grab them from
>          any GNU archive site.
 and
> /home/ce/Mesa-9.2.0-rc1/bin/missing --run autoconf
> /usr/bin/m4:aclocal.m4:1379: cannot open `m4/libtool.m4': No such file or
> directory
> /usr/bin/m4:aclocal.m4:1380: cannot open `m4/ltoptions.m4': No such file or
> directory

> 
> As far as I can see, fedora only seems to ship automake-1.13 - is this a
> problem?
> 
> Regards, Clemens


 built 9.2-git (d72f7720) a couple of times this week on
linuxfromscratch, based on the commands for 9.1.x in BLFS
http://www.linuxfromscratch.org/blfs/ (Read Online) without any
problems.  Those builds were on LFS-7.4-rc which uses automake-1.14.

 I'll note the following :

1. 9.2-rc2 is now out, so probably better to test that.

2. I provide a /usr/share/automake symlink to whichever version is
installed, i.e. to /usr/share/automake-1.14 on my current build.
Not sure if that makes any difference, it's just something I've
always done.

3. In BLFS we use a patch to build glxinfo and glxgears against the
current Mesa version.  The 9.1 version applies (strictly, I used
9.1.5 but I think 9.1.6 is probably a symlink to the same file).
This means that we *have to* run autoreconf.

4. In -rc2 I see the same problem as you if I just run configure and
then run make.

5. When I built the git version I used autoreconf -fi, apparently
without problems.  I've just tried -rc2  and for some reason the -i
option was rejected the first time, causing autoreconf to not operate.
Without it, I noticed that autoreconf ended in error.  But after that
I was able to configure and start the build.  I've now untarred it
again and successfully run autoreconf -fi.  Go figure!  Followed by
./configure, and make is now compiling various .lo files.

 So I suggest that you run autoreconf -fi ; ./configure

 Not sure if any of the developers actually read this list, but
something seems to be wrong.  I'm not subscribed to the development
list.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce