Hi Arrigo, All, I can talk about the python part, there I had the issue that you could not build against an external python, even if you configured that you want to build against a system- build. Configure was always using the internal config too. The build was licky because configure overwrites the external configs.
i could imagine that the implementation of configure for expat is not clean either. All the best Peter Am 13. Oktober 2025 09:03:27 MESZ schrieb Arrigo Marchiori <[email protected]>: >Hello Damjan, All, > >On Mon, Oct 13, 2025 at 03:01:33AM +0000, Damjan Jovanovic wrote: > >> On Sun, Oct 12, 2025 at 8:05 PM Arrigo Marchiori <[email protected]> wrote: >> >> > Hello All, >> > >> > I looked into the way expat is built and used in AOO. >> > >> > TL;DR: expat functions are partially taken from our expat, and >> > partially from system-level expat. >> > >[...] >> > >> > Why is the system-level libexpat.so calling internal functions of our >> > own statically linked expat? How can we avoid it? >> >> Try running AOO as: >> LD_PRELOAD=/path/to/system/libexpat.so soffice.bin >> >> Does that crash? > >I will try later from home. > >In the meantime, I fired up a VM with the lates OpenSUSE at work >and... it works well here! > >I could have done something wrong on my own system at home. I'll look >into that later. I wanted to share with you this... relieving >information. > >Best regards, >-- >Arrigo > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] >
