editors/openoffice-1.1 install problem on -STABLE

Andrew Reilly andrew-freebsd at areilly.bpc-users.org
Tue Apr 6 01:28:42 PDT 2004


Hi there,

I'm afraid that the upgrade to 1.1.1 seems to have provoked the
same problem that I had for 1.1.0 (which is installed, and runs
fine, now), and I can't remember how I fiddled that to make it
complete installation.  Perhaps someone here can remind me?

Situation: I've just (seemingly successfully) built
openoffice-1.1.1 from the editors/openoffice-1.1 port, but when
it comes to installation it stops at:

register uno component: /usr/local/OpenOffice.org1.1.1/program/libdate645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/libanalysis645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/libplacewarefi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/libsm645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/libsvg645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/libflash645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/liblth645fi.so
register uno component: /usr/local/OpenOffice.org1.1.1/program/pythonloader.uno.so
register configuration: ..................................................................................................................................................................................................................................................................................................................................................................................................

All of the dots after configuration: come out at a respectable
rate (a few per second), but at this point it just sits, and the
CPU use is at 100%.

If I break into the process with gdb521, there are three
threads, and the broken-into one is in:

0x280827c4 in sigprocmask () from /usr/libexec/ld-elf.so.1
(gdb) where
#0  0x280827c4 in sigprocmask () from /usr/libexec/ld-elf.so.1
#1  0x28080969 in symlook_obj () from /usr/libexec/ld-elf.so.1
#2  0x2807f4ca in dlopen () from /usr/libexec/ld-elf.so.1
#3  0x28c6fcad in osl_psz_loadModule ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/libsal.so.3
#4  0x28c6fc4b in osl_loadModule ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/libsal.so.3
#5  0x28a4a504 in cppu::loadSharedLibComponentFactory(rtl::OUString const&, rtl::OUString const&, rtl::OUString const&, com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory> const&, com::sun::star::uno::Reference<com::sun::star::registry::XRegistryKey> const&) ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/libcppuhelpergcc3.so.3
#6  0x29fcef97 in stoc_loader::DllComponentLoader::activate(rtl::OUString const&, rtl::OUString const&, rtl::OUString const&, com::sun::star::uno::Reference<com::sun::star::registry::XRegistryKey> const&) ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/shlibloader.uno.so
#7  0x28a3f85a in cppu::ORegistryFactoryHelper::createModuleFactory() ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/libcppuhelpergcc3.so.3
#8  0x28a3ef7a in cppu::ORegistryFactoryHelper::createInstanceWithArgumentsAndContext(com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&, com::sun::star::uno::Reference<com::sun::star::uno::XComponentContext> const&) ()
   from /usr/ports/editors/openoffice-1.1/work/sv002.tmp/libcppuhelpergcc3.so.3

(It is always thus.)

(gdb) i threads
  3 Process 50199, Thread 3  0x291ceefb in _thread_kern_sched ()
   from /usr/lib/libc_r.so.4
  2 Process 50199, Thread 2  0x291ceefb in _thread_kern_sched ()
   from /usr/lib/libc_r.so.4
* 1 Process 50199, Thread 1  0x280827c4 in sigprocmask ()
   from /usr/libexec/ld-elf.so.1

If I kill this process, then the port installation completes
anyway, but /usr/local/OpenOffice.org1.1.1/setup complains that
/usr/local/OpenOffice.org1.1.1/program/instdb.ins can't be
found, and that's the end of that.

Can anyone suggest how I can gently nudge the configuration
process to find whatever it's looking for and continue properly?

Yeah, yeah, install from the package.  I'm insufficiently
interested in openoffice itself to do that, but am quite willing
to help debug the build process so that that isn't necessarily
the default answer.  I *like* the port build process in FreeBSD.
I want it to work.

Cheers,

-- 
Andrew


More information about the freebsd-openoffice mailing list