Re: qhull external symbols clash

Andrew Nelson <[email protected]>
Newsgroups gmane.comp.python.scientific.devel
Message-ID <CAAbtOZfx3LwVKRQh57qDXLkX53r14xLP+Xsd4nWHNhECO+O3Yg@mail.gmail.com>
On Thu, 5 Jan 2023 at 17:33, Sam Gillingham <[email protected]>
wrote:

> Yes that's the file. It has all the qhull functions exported as their
> original names (look for functions starting with "qh_").
>
> Problem is if _qhull.cpython-310-darwin.so is already loaded and another
> library comes looking for qhull symbols it *may* get the scipy functions
> instead leading to incompatibility esp. if it is looking for a different
> version (as we saw on conda-forge).
>

That's quite interesting. I need to find out more about how symbol names
get resolved. I would've naively thought that if you had the same
function/symbol name in two files called libqhull.so and _
qhull.cpython-310-linux.so then they would resolve separately, doesn't the
loader use the library file name to find the symbols?

_______________________________________________
SciPy-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/scipy-dev.python.org/
Member address: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.