<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - Building 32 bit mesa on 64 bit OS fails since change for automake"
href="https://bugs.freedesktop.org/show_bug.cgi?id=50754#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - 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 <span class="vcard"><a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> <span class="fn">Alexandre Demers</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=50754#c23">comment #23</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=50754#c22">comment #22</a>)
> > I'm closing this bug because I'm able to crosscompile anytime with the help
> > of some variables.
>
> This is Mesa bug. You being able to work around Mesa bug doesn't mean that
> it's fixed in Mesa. Re-opening.
>
> IMHO either --enable-32-bit should be removed as misleading[1], or Mesa
> should be fixed.
>
> [1] as discussed, it sets CFLAGS/CXXFLAGS too late, so they don't have the
> required effect.
>
>
> Regarding Tapani's patch fixing this, there would need to be also a comment
> in configure.ac about the libtool initialization dependency on C/XXFLAGS
> values.</span >
The problem has been flagged many times. No decision has ever been taken.
Having a recurring bug like this one where it is a matter of either fixing it
or removing it shouldn't stay forever opened. When I closed it, because I had a
workaround, I was considering the silence on this bug and the other similar
ones as "WONTBEFIXED".
I'd be glad to either see it being fixed or dumped. As you say, if
--enable-32-bit is not working as intended for anybody, then it is misleading
and useless, thus it should be removed. In the Doc, we could indicate the
"workaround" (which is not a workaround per-se because it is actually the
detailed way of doing it instead of relying on an automated flag like
"--enable-32-bit").
We even have an almost (yet simple) patch proposed that only needs a little fix
as it seems.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>