RE: crash-on-start with incremental build ...

Should have replied to all...
> I had a similar (or even identical) message.
> re-make from clean did not help.
> What did help was this:
> source ooenv
> (I used ./ooenv previously, but ooenv can no longer be executed).
>
> I hope this helps :)
>
>
>
> Winfried
>
>
> > -----Oorspronkelijk bericht-----
> > Van: libreoffice-bounces+osc=dci-electronics.nl@lists.freedesktop.org
> > [mailto:libreoffice-bounces+osc=dci-electronics.nl@lists.freedesktop.o
> > rg]
> > Namens Michael Meeks
> > Verzonden: woensdag 23 mei 2012 13:34
> > Aan: libreoffice-dev
> > Onderwerp: crash-on-start with incremental build ...
> >
> > Hi guys,
> >
> >     Just a heads up: I am getting:
> >
> >     "The application cannot be started. Cannot activate implementation
> > file ... libdeployment.so: loading component library failed".
> >
> >     This is down to having an internal libxml2 in my solver/workdir and
> > building vs. the (apparently older/different) system libxml which is
> > missing the LIBXML2_GLOBAL_VARIABLES version.
> >
> >     Solution: prolly easiest to re-build from scratch[1].
> >
> >     and re-run 'make' :-) or of course, with lots of spare CPU time, re-
> > make from clean.
> >
> >     Digging at the dependencies, it makes me wonder why we indirectly
> > include tons of libxml headers across writer in order to get a single
> > struct forward definition - am testing a fix for that.
> >
> >     HTH,
> >
> >             Michael.
> >
> > [1] - I tried something like:
> >     rm -Rf libxml2/unxlngi6.pro libxmlsec/unxlngi6.pro
> >     find workdir solver -name '*libxml*' | xargs rm -Rf
> >     find workdir -name '*.d' | xargs rm
> >     make l10ntools.clean jvmfwk.clean
> > --
> > michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot
> >
> > _______________________________________________
> > LibreOffice mailing list
> > LibreOffice@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/libreoffice