Bug 51749

Summary:	make[6]: ../../../../src/mesa/Makefile.old: No such file or directory
Product:	Mesa	Reporter:	Fabio Pedretti <pedretti.fabio>
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	medium
Version:	git
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Fabio Pedretti 2012-07-05 04:59:44 UTC

Current mesa git fails to build with:

make[5]: Leaving directory `/build/buildd/mesa-8.1~git1207051336.33526a~gd~p/build/swx11+glu/src/mesa/x86-64'
Making all in .
make[5]: Entering directory `/build/buildd/mesa-8.1~git1207051336.33526a~gd~p/build/swx11+glu/src/mesa'
make -f ../../../../src/mesa/Makefile.old
make[6]: Entering directory `/build/buildd/mesa-8.1~git1207051336.33526a~gd~p/build/swx11+glu/src/mesa'
make[6]: ../../../../src/mesa/Makefile.old: No such file or directory
make[6]: *** No rule to make target `../../../../src/mesa/Makefile.old'.  Stop.

Full log here:
https://launchpadlibrarian.net/109374107/buildlog_ubuntu-precise-i386.mesa_8.1~git1207051336.33526a~gd~p_FAILEDTOBUILD.txt.gz

Comment 1 Matt Turner 2012-08-07 21:49:33 UTC

Not a problem now, right?

Comment 2 Fabio Pedretti 2012-08-09 11:49:05 UTC

(In reply to comment #1)
> Not a problem now, right?

Last time I checked (3 weeks ago) compilation failed before this point, see the full log:
https://launchpadlibrarian.net/110234722/buildlog_ubuntu-precise-i386.mesa_8.1~git1207161211.81de04~gd~p_FAILEDTOBUILD.txt.gz
so we can't say if it's fixed now.

I also suppose this last issue is still not fixed since I saw two patch series on the ML that should fix out of tree builds but that still aren't in git. I cannot retest until some weeks however.

Comment 3 Matt Turner 2012-08-09 14:53:09 UTC

Out of tree builds aren't fixed yet, but Makefile.old does't even exist anymore, hence my question.

Comment 4 Fabio Pedretti 2012-08-20 10:42:32 UTC

Confirmed fixed.

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.