> Stripping away some of my redundant geekberish, the rule is
> simple enough:

Oh my, that was a lot of info. I'll need to save and keep as a reference!

> > The peculiar thing about this problem is only kword and kpresenter are
> > affected. Possibly there are other "undefined symbol" problems in my
> > builds that I have not yet noticed, but I'm guessing kword and
> > kpresenter are not linking correctly during my builds. I don't know
> > how to debug further or what to look for.
> 
> You might find the linker flag --no-undefined (-Wl,--no-undefined in
> LDFLAGS) to be useful. (I thought Trinity was passing it already, but I
> could be wrong.)

The build log is filled with --no-undefined. I presume the flag is used when building kword and kpresenter too, although I did not try to filter the log that deep.

> Other more-or-less-obscure things you might find useful in this hunt:
> 
>  - dynamic linker symbol debugging, set LD_DEBUG=symbols before running
>    the program: very verbose: see also LD_DEBUG=help (then run any
>    dynamically-linked program at all, e.g. LD_DEBUG=help ls)

Yesterday I toyed a bit with the LD_DEBUG variable. LD_DEBUG=symbols took so long that I gave up and interrrupted the output. I have no idea what to look for in that output.

>  - linker symbol tracing, -Wl,--trace-symbol=SYMBOL in LDFLAGS,
>    which prints every file the named symbol appears in

I'm not following with that one. Exactly what do I do?

Darrell