Alan Lord wrote:
This was from a different message - not from me! I have only installed
the JDK _06 binary.
Actually, I was replying to both messages at once. :-)
I do think that my attempts at building OOo were *nearly* successful as
the build directory grew to about 3Gb during the process and, like I
said, took about 4-5 hours to get there. My host is a (quite old) 2.6Ghz
P4 (400Mhz FSB) with 256M RAMBUS RAM and 512M of swap.
Well, I was successful with jdk-1.5.0_05 build from source and OOo
build. Unfortunately, the configure check is broken for BDB in
OOo-2.0.1, so I used the internal version without the db4.4 patch.
Configure couldn't determine the version string, but I don't imagine
that'll be difficult to fix. For patching, I used the patches that had
not been applied upstream from the original blfs patchset, and then two
additional jdk-1.5 changes. I don't know how the xalan stuff got back
into xmlhelp, but it hasn't been needed for a while, so just remove the
imports there...and then also xmlhelp, three enums (changed to
uenum...doesn't really matter what you call them).
This was on slightly modified udev_update branch with en_US-UTF8 and
Xorg-6.9.0. Had the minimum requirements for OOo with added python,
startup-notification, and cups. I'm restoring my clean system now to
start on Xorg-7.0. Just FYI, I'd have to review the previous thread,
but I believe the book will be moving the installation directory default
for Xorg-7.0.
Actually, Bruce, what was decided? I can't find the thread where we had
discussed this before. /usr/X11 as the default with /usr as the option,
similar to the way it is now. :-/ I prefer the /usr method as default
now for the book as that is what the distros seem to be doing...less
chance for breakage that way later on down the road (but I'll use a
separate installation path for myself). In either case, both Xorg-6.9
and 7.0 must be updated to account for this...(luit's parser.h has a
hardcoded reference to /usr/X11R6 as mentioned previously by Alexander,
and mesa code has 'em all over the place, the reason for the blind,
recursive sed in the mesa instructions in my homedir).
The last failures were something to do with dictionaries or language
features I seem to recall, even though in my last attempts I had removed
all "foreign" switches (UK lang and dict options).
Hope this might help...
It'll give me something to look at. I had intended to give the
alternate provided languages/locales? some better coverage anyway.
Alan
PS - Glad your son is better. I hate it when my kids get ill - nothing
worse in the world for making you worry!
Thank you. He's back to himself now....driving me nuts with 'why?' as
is the norm for a 3yo I'm told. :-)
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
