A loader symbol lookup error probably means that the dynamic library loaded during runtime differs from the one that was assumed during compile time. "agg" is a component of matplotlib, so it could be that the inconsistency lies within matplotlib itself. Could it be the case that an old version of a library is hanging around in ~/.local or something like that, which ends up shadowing the actual (hopefully freshly installed) version of the library? There are some big changes in the build/installation system in sage-10.7, so it could be that an artifact that was previously harmless now gets in the way. While you're waiting for an expert, you could try and see if building/running in a cleaner environment makes the problem go away.
On Tuesday, 26 August 2025 at 16:14:39 UTC-7 Richard_L wrote: > 1) Sorry, I forgot to mention, I am building sage-10.7 from source on > openSUSE-15.6. > 2) It turns out not to matter whether sage builds matplotlib or if it is > installed from the OS repository. > > Suggestions welcome. > > On Tuesday, August 26, 2025 at 8:35:04 AM UTC-7 Richard_L wrote: > >> All(?) tests invoking matplotlib show at least one of two error messages. >> See attachment "plot_fail". However, the build finished and reported >> success (install.snip), while 'make ptestlong' shows 200+ errors >> (test.log). Neither matplotllb nor matplotlib-inline report failure. [ >> Note: install.log too big to attach; therefore the tail of install.log >> attached here as install.snip. ] >> Please inform if some other log file is needed to debug this. >> Thanks >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/2dd3ab2b-ab8b-4f33-b245-987cced93ab8n%40googlegroups.com.
