Bug 58812

Summary:	Infinite loop in ./configure && make if automake is absent
Product:	Mesa	Reporter:	Arseniy Alekseyev <rotsor>
Component:	Other	Assignee:	mesa-dev
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	medium	CC:	mattst88
Version:	9.0
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	Build log

Description Arseniy Alekseyev 2012-12-27 17:55:41 UTC

Created attachment 72194 [details]
Build log

The make command keeps calling configure and looping forever, unless autoconf is present. To exactly reproduce the build you can instantiate the following Nix expression with a recent nixpkgs snapshot. The build log is attached. The section below "THE FOLLOWING REPEATS" is repeated forever.

{ stdenv, fetchurl, flex, bison, pkgconfig, libdrm, file, expat, makedepend
, libXxf86vm, libXfixes, libXdamage, glproto, dri2proto, libX11, libxcb, libXext
, libXt, udev, enableTextureFloats ? false
, python, libxml2Python, autoconf, automake, libtool, llvm }:

let version = "9.0.1"; in

stdenv.mkDerivation {
  name = "mesa-${version}";

  src = fetchurl {
    url = "ftp://ftp.freedesktop.org/pub/mesa/${version}/MesaLib-${version}.tar.bz2";
    sha256="0vyvfl56ac8d7s5avi2f4dad82jzxwkf17wjq1yklgyfpa1vm9sp";
  };

  buildInputs = [ expat libdrm libXxf86vm libXfixes libXdamage glproto dri2proto
    libxml2Python libX11 libXext libxcb libXt udev llvm ];

  buildNativeInputs = [ pkgconfig python makedepend file flex bison ];
}

Comment 1 Matt Turner 2013-01-18 21:17:11 UTC

This seems odd. It looks like the Nix build system might be patching or modifying some autoconf/automake generated file. Can you reproduce this manually?

Comment 2 Arseniy Alekseyev 2013-01-26 19:01:16 UTC

(In reply to comment #1)
> This seems odd. It looks like the Nix build system might be patching or
> modifying some autoconf/automake generated file. Can you reproduce this
> manually?

I've tried to build it with a custom builder, seeing the same result. The code for the custom build script is:

    . ${stdenv}/setup
    tar xf $src
    cd Mesa*
    ./configure
    make

You can see that there is nothing weird happening between untarring and making, meaning the Mesa source code is intact ($src points to the original tar). Now there could be some weirdness in in nixpkgs standard environment causing this, but I don't know which.

Comment 3 Matt Turner 2013-03-06 19:33:13 UTC

Still not sure what causes this, but I saw another report of it on IRC today. The reporter said that installing libtool (which he didn't previously have) and regenerating the autoconf files (via ./autogen.sh) fixed the problem for him.

Comment 4 Matt Turner 2015-05-20 21:06:16 UTC

I assume this has been fixed since we're now using make dist to generate the tarballs. Reopen if not.

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.