Try running JupyterLab in a shell with `export LD_DEBUG=libs` and import sage with that jupyterlab instance. That should tell you where givaro is loaded from.
Isuru On Wednesday, May 31, 2023 at 2:46:14 PM UTC-5 Isuru Fernando wrote: > That's a different issue than this. > > Isuru > > On Wed, May 31, 2023 at 2:37 PM Jan Groenewald <jan.gro...@gmail.com> > wrote: > >> Hi >> >> This >> https://groups.google.com/g/sage-support/c/egP7I9eGLuI/m/MsUUNLEUAQAJ >> suggests trying clang 14 for compiling sage or waiting for givaro >> compiled with clang 15. >> >> (or just try rebuild the deb for givaro with clang15 >> https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/) >> >> Regards, >> Jan >> >> On Tue, 30 May 2023 at 18:48, Nils Bruin <nbr...@sfu.ca> wrote: >> >>> On Tuesday, 30 May 2023 at 06:09:23 UTC-7 Luis Finotti wrote: >>> >>> >>> I looked at it, but I cannot tell if it is really the same issue, or how >>> I could check. >>> >>> well ... it looks like the symbol that is found undefined is indeed of >>> the type mentioned there. So that would suggest that indeed a system givaro >>> is picked up while sage is apparently compiled with a "too advanced" c++ >>> ABI for that library. However, you're not getting errors when you just run >>> sage-10.0, so it would seem there is a givaro library that can satisfy the >>> needs (it probably built its own givaro) >>> >>> So in your case there seems to be something about the environment in >>> which jupyter starts sage that confuses the library resolution process. I >>> imagine it could be something where juoyter runs using a python that has >>> its own venv and that the initialization of sage (which should set up its >>> venv) somehow misses overriding something or erroneously inherits something >>> from the jupyter venv. >>> >>> In that case I would expect this issue was basically always present, but >>> has only recently become relevant because now the system givaro doesn't cut >>> it any more. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "sage-support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to sage-support...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/sage-support/24724ea0-edcc-4470-8b30-56cde325caf2n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/sage-support/24724ea0-edcc-4470-8b30-56cde325caf2n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-support...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-support/CAAg%3Dp_0OtZQBbEV4oN8pFJshScF8L_xJ-bphtQ6EH5nixwshvg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/sage-support/CAAg%3Dp_0OtZQBbEV4oN8pFJshScF8L_xJ-bphtQ6EH5nixwshvg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/42a5c154-4ed6-411a-93d3-3ffbdaa61c72n%40googlegroups.com.
