<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Building 32 bit mesa on 64 bit OS fails since change for automake" href="https://bugs.freedesktop.org/show_bug.cgi?id=50754#c32">Comment # 32</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Building 32 bit mesa on 64 bit OS fails since change for automake" href="https://bugs.freedesktop.org/show_bug.cgi?id=50754">bug 50754</a> from <a class="email" href="mailto:mattst88@gmail.com" title="Matt Turner <mattst88@gmail.com>"> Matt Turner</a> <pre>(In reply to <a href="show_bug.cgi?id=50754#c30">comment #30</a>) > (In reply to <a href="show_bug.cgi?id=50754#c29">comment #29</a>) > > While this patch looks correct at first sight I caused quite a few issues > > with other parts of mesa. As such I've reverted it, removed the hacky > > --enable-32,64-bit options, and documented (docs/autoconf.html) a reasonable > > approach towards multilib/cross-compile builds. > > Could you document here what kind of issues it causes? I don't think that's particularly useful to document in autoconf.html. Basically, the --enable-{32,64}-bit flags were neither necessary nor sufficient. configure.ac is not supposed to modify CFLAGS/CXXFLAGS. The --enable-{32,64}-bit flags operated by doing exactly that, and as such they didn't work (see this bug) and caused other problems. To work around this bug, you ended up setting -m32 in your CFLAGS anyway, so the only thing these flags did was to set the assembly architecture. Setting the --build and --host does that anyway. So throwing out these hacks is the right thing to do.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>