<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - BUILD FAILED: why : forced (dist) upgrade for gcc 3.4.6 over a BIT COUNT, __builtin_ctz"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86368#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - BUILD FAILED: why : forced (dist) upgrade for gcc 3.4.6 over a BIT COUNT, __builtin_ctz"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86368">bug 86368</a>
from <span class="vcard"><a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> <span class="fn">Emil Velikov</span></a>
</span></b>
<pre>Dear debguy/johnandsara2
As Matt, pointed out bashing is not most appropriate way to approach any person
or project.
Additionally I'm not sure why you build the radeon code, considering that
(based on your statement) you're not using it.
If you have a patch that adds a fall back in case of missing __builtin_ctz(old
compiler etc.), that follows the surrounding coding style, please submit it to
the dri-devel mailing list via git send-email.
Thanks
P.S. Using autoconf macros might be a nice way to detect the presence of
__builtin**. Take a look at the mesa project if you'd like an example.</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>