Thomas Steffen wrote:
I tried that, but gave up pretty soon. The basic problem is that
Oracle is compiled for a hybrid system, that has 32bit libraries in
/lib and 64bit libraries in /lib64. Only a few components are actually
64bit, while most GUI tools (including the installer, IIRC) are in
fact 32bit executables.
More than anything, it's builtin JRE is 32-bits, and it's very hard to
get it to use anything else.
That's causing the problem Faheem is having with the installer.
Installing the appropriate 32-bit X libraries and setting the
environment to point to the 32-bit locale should let him limp along.
Also, he made need -dev files for a 32-bit toolchain as well as 64-bit.
My install failed and I didn't pick it back up, as the need passed.
You can install 32bit libraries in
different ways, but obviously not in /lib, where they are expected.
AFAIK, with the exception of the X locale issue, Oracle is well behaved
and doesn't actually care; as long as ld.so knows where the library is,
you are OK.
I could be mistaken though.
The sun package? That did not work very well for me, I had lots of
crashes. And it is possible that Oracle needs a 32bit version (in
addition?).
The sun 64-bit JRE is buggy, but less buggy than any other one.
One more interesting thought: it may be easier to start with a 32bit
version of Debian, and add the 64bit libraries necessary to run the
Oracle server in /lib64. You need at least testing for this to work,
but it should get a lot closer to the hybrid system expected by
Oracle. You can also do this in a chroot.
This is quite likely correct.
Note in all cases, a chroot may make things somewhat harder, as you
still need a 32-bit JRE and a 64-bit toolchain to do 64-bit Oracle
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]