hi Jonathan,
Don't use 'export LD_PRELOAD'. When you set this dld.sl will preload
libjava.sl for all the application, and there is a known problem with
LD_PRELOAD which is documented in dld.sl man page.
----
Note: Using LD_PRELOAD can cause a core dump when used with
applications which mix shared and archived libraries, especially
when both the shared library and the application are built with aC++
or use libc.
----
Hence use LD_PRELOAD only for the application u want to run. for eg.
bash-2.01$ LD_PRELOAD=/lab1/u01/app/oracle/product/8.1.6/JRE/lib/PA_RISC/
native_threads/libjava.sl make test
thanks,
Ranjith.
Hi Lincoln,
Thanks for your help with this. We now have a working
installation, although we still do have some issues to resolve still. The
problem seems to be the libjava.sl library. Running the make test step
generated this message: Can't shl_load() a library containing Thread Local
Storage. We have got round this by setting the LD_PRELOAD to point to the
library - $ORACLE_HOME/JRE/lib/PA_RISC/native_threads/libjava.sl. The make
test passes OK, and make install works. My DBI test script is able to do
some basic stuff, so presumably it is OK. There are some problems
remaining with it, though. You have to set the LD_PRELOAD variable before
running any perl against Oracle (as I guess the library does not get built
into the DBD). We have also noticed that if you set LD_PRELOAD as above,
then run swlist, the system coredumps (swlist works normally without this
set). This worries me, as it may cause other commands to coredump, so we
will need to try to extensively roadtest this before we can move into
production. The libjava.sl library is only required for an advanced
authentication module that we do not use, so we are hoping that we can
remove this from our Oracle installation, and get around the problem this
way. We did manage to install DBD on one of our boxes before Xmas without
this problem, so we know that it can be done, we have just lost the recipe
that we need. If anyone has any suggestions that we could try, we would be
grateful. It is also worth noting that this error was what hung us up
trying to get gcc to work, so with this option, we may be able to push
forward on this. We will give it a go on another box, and post if we get
any joy from this. I have included the recipe that we have used
below. This does produce a working build, we are just a little concerned
about the side effects. Cheers,
Jon
--
@ 91-80-2051073 (off)
91-80-6583830 (res)
