<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] 0d108116bd80b757fb01a84a9f1946ef870b57b8 breaks osmesa when cross compiling" href="https://bugs.freedesktop.org/show_bug.cgi?id=59737#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] 0d108116bd80b757fb01a84a9f1946ef870b57b8 breaks osmesa when cross compiling" href="https://bugs.freedesktop.org/show_bug.cgi?id=59737">bug 59737</a> from <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=59737#c3">comment #3</a>) > (In reply to <a href="show_bug.cgi?id=59737#c2">comment #2</a>) > > I'll try with the --build and --host options, however it was not needed > > before. Also, I'm wondering why they should be set if we have > > --enable-32-bit and --enable-64-bit options we can push at autogen.sh. > > --build and --host is how autotools cross compiles. > > > These > > two options should take care of it. Otherwise, they are useless and they > > should be removed. > > They haven't worked in years, so.. :) Good news, it works with the options. I've been able to remove other variables I had to set to make it work before. I still need to set LLVM_CONFIG though. In the past, I was able to use --enable-XX-bit without any magic until about a year ago. Then, I added CFLAGS and CXXFLAGS with some paths for libraries. But if you tell me the options are broken and won't be fixed, I'm in favor of getting --enable-XX-bit out and documenting how to use the --build and --host options. I think this bug can be closed, but devs should take position about getting rid of the --enable-XX-bit options.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>