I'm afraid not. As per the BLFS instructions, the build process should have left the "installed" package under the directory instsetoo_native/unxlngi6.pro/OpenOffice ! It didn't happen in my case. As the BLFS Book mentions installing epm as an optional dependency for OO, I installed it prior to compiling OO. OO ships with its own patched version of epm but, if it finds system installed epm, it uses that. System intalled epm (version 4.0) doesn't respect product names containing characters other than letters and numbers while, OO specifies product name containing hyphens and dots ! This results in epm stop with an error and thus the build does not produce the package. After four days of struggle and with the help of experts on OO dev mailing lists I figured out how to get the product delivered. I'd to specify --with-epm=internal and that did it.

I'd say there should be a note in BLFS Book where it lists  epm as an optional dependency which would warn the users of the obvious pitfall !

Kevin

On 11/10/06, Chris Staub <[EMAIL PROTECTED]> wrote:
Kevin Williams wrote:
> I tried searching thru' the forums/mailing lists of openoffice.org, I
> don't see any thread that is related to compiling openoffice. All the
> threads I see on openoffice.org are related to installing and setting
> up binary versions !
>
> Fortunately enough, I stumbled upon a page on openoffice.org that
> briefly summarizes the build process. From there I learned that, the
> build process outputs all binaries, libs, includes etc. to the
> directory solver. When I look into the directory
> solver/680/unxlngi6.pro, I do see several directories - bin, lib, inc,
> rdb, res etc. Thses in turn hold the libs and binaries etc. Now, I
> know where the finished product lies. What I'm mused over is - do I
> copy these directories to /opt/OpenOffice2 and presume this is the
> right way to do. ?
>
> The page in question - http://tools.openoffice.org/background.html -
> explains that if one changes to the directory instsetoo_native and
> runs 'build --all', the build script will build all the modules and
> delivers them. I couldn't figure out where it delivers !!? I were
> wondering if I run this 'build -all' would it result in rebuilding the
> entire tree or would it behave like a standard make, I mean traverse
> thru' directoried and  find that all the targets have been made and
> only deliver the package to wherever it delivers ? I wouldn't want to
> rebuild the entire tree again after having spent three days int just
> this one !!
>
> Can someone do me a favour by mailing me a file that contains a list
> of the files (with qualified paths) that will be installed to the
> destination. A simple 'find /opt/openoffice' should do it.
>
> Also, I would appreciate if someone could confirm if all the programs
> that are installed namingly,  scalc, sdraw, simpress, smath, soffice
> and swriter  actually are shell scripts and not elf binaries !
> (spadmin - Not found. But I do see an elf binary named spadmin.bin)
>
> Thanks for any help that would come along.
>
> Kevin

I don't understand the problem. Did the BLFS instructions not work for you?
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to