Greetings,
I have built OOH680_m10 on ubuntu-Gutsy (7.10). Somewhere between
creation of libraries in the solver and installing from the rpm's, I
lose debugging symbols.
I configured with
--enable-symbols
and built with
dmake debug=true
The build process produces lines ...
checking whether to strip the solver or not.... checking whether to
enable native CUPS support... yes
(yes that is one line), and ...
The variable DISABLE_STRIP is set to: TRUE
checking whether stripping libraries is possible... yes
and then only 17 lines apart close to the end of the build ...
make_installer.pl, version 1.0
Stripping files
so I suspect that the loss occurs before the .rpm files are created.
After another configure with --disable-strip-solver, another dmake
debug=true recreated the .rpm files, but they are only very slightly
bigger than before and still the installed files lack debugging
symbols.
I can access the debugging symbols by linking from my installed
directory back to the files built in the solver. Is there a more
straight-forward way?
Here are some details ...
The earlier configure command reads, with line-breaks added here for
readability ...
./configure_fudge
--disable-mozilla --with-stdlibs --with-system-zlib
--with-system-openssl --with-system-jpeg --with-system-expat
--with-system-freetype --with-system-libwpd --with-system-python
--with-system-db --with-system-hsqldb --with-system-beanshell
--with-system-sml-apis --with-system-xerces --with-system-xalan
--with-system-libxslt --with-system-odbc-headers
--with-system-sane-header --with-system-xrender-headers
--with-system-curl --with-system-boost --with-system-vigra
--with-system-neon --with-system-hunspell --with-system-odbc
--with-system-sane-header --disable-pasf --without-fonts
--without-dict --disable-odk --without-myspell-dicts
--with-package-format=rpm --enable-symbols
I hacked configure_fudge from configure to accept hsqldb 1.8.0.8
instead of hsqldb 1.8.0.9 which the distributed configure requires.
(Well, I guess that in itself is grounds for another question soon.)
I still have output from the build, but it is really big. The
installation script is homebrewed (before I learned about
unxlngi6.pro/bin/userscripts/install). The central part, following
the pattern of OpenOffice.org 2.0 Setup Guide, page 39, is ...
rpm --install \
--dbpath $RPMDB \
--nodeps \
--prefix $DESTDIR \
~/OOo_hacking/${WHAT}/instsetoo_native/unxlngi6.pro/OpenOffice/rpm/install/e
n-US/RPMS/*.rpm
I must presume that I am missing something really obvious. Thank you
for your attention.
Terry.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
