<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Undefined non-weak-symbol in dri-drivers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98428#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Undefined non-weak-symbol in dri-drivers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98428">bug 98428</a>
from <span class="vcard"><a class="email" href="mailto:ajax@nwnk.net" title="ajax at nwnk dot net <ajax@nwnk.net>"> <span class="fn">ajax at nwnk dot net</span></a>
</span></b>
<pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=98428#c7">comment #7</a>)
<span class="quote">> So... how does it work if the linked libglapi and libGL provide different,
> incompatible implementations of, say, _glapi_set_dispatch?</span >
Define "incompatible". If they have the same interface from the caller's
perspective (same function names and signatures, and either compatible or
opaque data types), then everything's fine, ld.so will consistently pick the
same library in the search scope to provide those functions. I don't think the
glapi caller actually knows the layout of the dispatch table, for example, so
that could be whatever the implementation wants.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>