Bug#425863: FTBFS: teckit/libtool yields multiple definition errors

[ucko@debian.org (Aaron M. Ucko)]

Frank Küster <frank@debian.org> writes:

> Hm, I'm curious why this happens now.  The only changes to the build
> process that we made between -7 and -8 was to add the configure options
> "--enable-shared --enable-ipc".  We don't want to create a shared teckit
> library, nor link dynamically to that code.  Hell, did we do that?

Just the former, AFAICT.

> No, it seems it is statically linked into xetex. 

Right, the only thing that uses TECkit is xetex, which explicitly
links statically against ../../libs/teckit/lib/.libs/libTECkit.a.
(OTOH, it could stand to link dynamically against libkpathsea.)
 
> Have you checked that it works, and on which architectures?

I ran a test build on my amd64 machine and encountered no errors.
 
> Maybe it's safer to patch teckit to ignore --enable-shared?

It looks like it should be possible to avoid patching anything by
changing --enable-shared to --enable-shared=default (as TECkit and
other third-party libraries set PACKAGE); the corresponding test build
is still in progress, but I'll be sure to let you know how it goes.

> We'll do our best, but I'd like to make sure it's the right fix.

Understood.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger amu@monk.mit.edu (NOT a valid e-mail address) for more info.