<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - assembly enabled mesa crashes dota2" href="https://bugs.freedesktop.org/show_bug.cgi?id=90383#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - assembly enabled mesa crashes dota2" href="https://bugs.freedesktop.org/show_bug.cgi?id=90383">bug 90383</a> from <a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> Tapani Pälli</a> <pre>(In reply to Sylvain BERTRAND from <a href="show_bug.cgi?id=90383#c8">comment #8</a>) > I tried -m32. Did not change anything. -m32 and -m64 are only for a gcc > multilib toolchains. Here, it's a normal x86 toolchain, with i686-pc-gnu-gcc > calling i686-pc-gnu-as (I checked i686-pc-gnu-gcc verbose output). > Did you mean something is hardcoded in the build system for the availabily > of the -m32/-m64 flags? If yes, what is it? Did you have also '--build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu'? It could be that '-m32' is not necessary here (I would not count on it though because I believe libtool needs it) but at least the build and host arguments are *very* necessary because libtool makes decisions based on them. So when you feed these to autogen.sh, it should generate you proper libtool file contents.</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>