On 17-Nov-2017 02:35, Eduard Braun wrote:
Background is a conflicting function name in libwmf and libuemf that caused some crashes [1] and was fixed by Tav by renaming the function in libuemf [2] which works as we have a copy of that library but obviously will cause issues if we attempt to update the library with upstream code at some point in the future.
What part of the code is using libwmf? Is libemf linked in too? I wrote libuemf because libemf didn't do everything it needed to (at least at the time) to fully enable emf support and then later expanded it to support wmf as well. I vaguely recall that there was some generic import/export mechanism available in Inkscape at the time which could be set to do emf but that the results were so limited that it was hardly worth the bother.
Anyway, since libuemf and (libemf + libwmf) are two separate implementations covering the same specialized data types it is hardly surprising that they have name conflicts. Normally a program would only use one or the other, and _that_ is the proper way to avoid these particular function name conflicts. Perhaps that is not possible here, if the code linking in libemf/libwmf is itself in an outside library which comes prelinked to the other two.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech