<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - python required to build Mesa release tarballs" href="https://bugs.freedesktop.org/show_bug.cgi?id=89328#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - python required to build Mesa release tarballs" href="https://bugs.freedesktop.org/show_bug.cgi?id=89328">bug 89328</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to Samuel Iglesias from <a href="show_bug.cgi?id=89328#c3">comment #3</a>) > I wrote a patch (attached) that removes the python mako module check when > python is not installed in the system. If it needs to do something with > python, it is going to fail anyway. > True. > If you think this patch is interesting to have in master, just say so and I > will send this patch to the mailing list. > Imho the patch looks good. Alternative solution is to have the macro set a variable that we check in configure (like below), but let see what others think on the ML. PYTHON_MAKO_REQUIRED=0.3.4 AX_CHECK_PYTHON_MAKO_MODULE($PYTHON_MAKO_REQUIRED) if test -n "$PYTHON2" -a $foo_mako_found = no; then AC_MSG_ERROR([Python mako module v$PYTHON_MAKO_MODULE not found]) fi Thank you Samuel!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>