Bug 96238

Summary:	swr fails to build outside of the main directory
Product:	Mesa	Reporter:	Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b>
Component:	Drivers/Gallium/swr	Assignee:	mesa-dev
Status:	RESOLVED FIXED	QA Contact:	mesa-dev
Severity:	normal
Priority:	medium	CC:	franck.delache
Version:	git
Hardware:	x86-64 (AMD64)
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Jan Ziak (http://atom-symbol.net) 2016-05-27 07:48:39 UTC

Executing something like this fails:

$ cd mesa
$ mkdir ../build64
$ cd ../build64
$ ../mesa/configure ... --with-gallium-drivers=swr,...
$ make

Output:

gen_llvm_types.py: error: argument --output/-o: can't open 'rasterizer/jitter/state_llvm.h': [Errno 2] No such file or directory: 'rasterizer/jitter/state_llvm.h'
Makefile:2009: recipe for target 'rasterizer/jitter/state_llvm.h' failed
make[3]: *** [rasterizer/jitter/state_llvm.h] Error 2
make[3]: *** Waiting for unfinished jobs....
usage: gen_llvm_ir_macros.py [-h] [--input INPUT] --output OUTPUT [--gen_h]
                             [--gen_cpp] [--gen_x86_h] [--gen_x86_cpp]
gen_llvm_ir_macros.py: error: argument --output/-o: can't open 'rasterizer/jitter/builder_gen.h': [Errno 2] No such file or directory: 'rasterizer/jitter/builder_gen.h'
Makefile:2015: recipe for target 'rasterizer/jitter/builder_gen.h' failed

Comment 1 Emil Velikov 2016-05-30 09:41:27 UTC

Should be fixed with:

commit 04987ef229f9f45f4452c95e894fcff980f84776
Author: Emil Velikov <emil.velikov@collabora.com>
Date:   Fri May 27 15:35:44 2016 +0100

    swr: automake: attempt to fix the out-of-tree build
    
    Make sure that the output folder is created otherwise the python scripts
    yells at us.
    
    Cc: 0xe2.0x9a.0x9b@gmail.com
    Cc: Tim Rowley <timothy.o.rowley@intel.com>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96238
    Signed-off-by: Emil Velikov <emil.velikov@collabora.com>

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.