Bug 89088 - Mesa fails to build if indent does not support requested arguments (eg: -nut)
Summary: Mesa fails to build if indent does not support requested arguments (eg: -nut)
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 10.4
Hardware: Other All
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-11 19:06 UTC by Jeremy Huddleston Sequoia
Modified: 2016-02-13 09:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jeremy Huddleston Sequoia 2015-02-11 19:06:58 UTC
make[4]: Entering directory `/opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_x11_mesa/mesa/work/Mesa-10.4.4/src/mapi/glapi/gen'
/opt/local/bin/python2.7  ../../../../src/mapi/mapi_abi.py \
		--printer glapi --mode lib ./gl_and_es_API.xml > ../../../../src/mapi/glapi/glapi_mapi_tmp.h
/opt/local/bin/python2.7  gl_procs.py -c -f ./gl_and_es_API.xml > ../../../../src/mapi/glapi/glprocs.h
/opt/local/bin/python2.7  gl_apitemp.py -f ./gl_and_es_API.xml > ../../../../src/mapi/glapi/glapitemp.h
/opt/local/bin/python2.7  gl_table.py -f ./gl_and_es_API.xml > ../../../../src/mapi/glapi/glapitable.h
/opt/local/bin/python2.7  gl_gentable.py -f ./gl_and_es_API.xml > ../../../../src/mapi/glapi/glapi_gentable.c
/opt/local/bin/python2.7  gl_enums.py -f ./gl_and_es_API.xml > ../../../../src/mesa/main/enums.c
/opt/local/bin/python2.7  gl_genexec.py -f ./gl_and_es_API.xml > ../../../../src/mesa/main/api_exec.c
/opt/local/bin/python2.7  gl_table.py -f ./gl_and_es_API.xml -m remap_table > ../../../../src/mesa/main/dispatch.h
/opt/local/bin/python2.7  remap_helper.py -f ./gl_and_es_API.xml > ../../../../src/mesa/main/remap_helper.h
/opt/local/bin/python2.7  glX_proto_send.py -f ./gl_API.xml -m proto \
	  | indent -i4 -nut -br -brs -npcs -ce -TGLubyte -TGLbyte -TBool > ../../../../src/glx/indirect.c
indent: Command line: unknown parameter "-nut"
Traceback (most recent call last):
  File "glX_proto_send.py", line 1126, in <module>
    printer.Print( api )
  File "/opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_x11_mesa/mesa/work/Mesa-10.4.4/src/mapi/glapi/gen/gl_XML.py", line 120, in Print
    self.printBody(api)
  File "glX_proto_send.py", line 346, in printBody
    self.printFunction(func, func.name)
  File "glX_proto_send.py", line 443, in printFunction
    self.printRenderFunction(func)
  File "glX_proto_send.py", line 901, in printRenderFunction
    self.common_emit_args(f, "gc->pc", 4, 0)
  File "glX_proto_send.py", line 492, in common_emit_args
    self.common_emit_one_arg(p, pc, adjust, extra_offset)
  File "glX_proto_send.py", line 482, in common_emit_one_arg
    % (pc, p.offset + adjust, src_ptr, p.size_string() )
IOError: [Errno 32] Broken pipe
/opt/local/bin/python2.7  glX_proto_send.py -f ./gl_API.xml -m init_h > ../../../../src/glx/indirect.h

Note that what makes this even worse is that subsequent 'make' invocations will eventually continue because the generated header files still get created (incorrectly) despite the error.
Comment 1 Matt Turner 2015-02-11 20:29:16 UTC
A commit was made recently to require GNU indent:

commit efef6c828092702b1f928f98d15fb90b4544a85c
Author: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Date:   Tue Jan 13 11:02:27 2015 +0100

    configure: add check for GNU indent

Do you have this in your tree?
Comment 2 Jeremy Huddleston Sequoia 2015-02-11 22:29:32 UTC
No, I was encountering this on the MacPorts Snow Leopard buildbot after updating mesa from 8.0.5 to 10.4.4.  We should probably cherry-pick that into 10.5 and 10.4.
Comment 3 Matt Turner 2015-02-11 23:10:06 UTC
Okay. Please send a cherry-pick request to mesa-stable@lists.freedesktop.org.
Comment 4 Timothy Arceri 2016-02-13 09:17:33 UTC
Assuming this made it to stable and closing. If not there is not much that can be done now.


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.