<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=koi8-r" http-equiv=Content-Type>
<META content="MSHTML 5.00.3103.1000" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Я тоже натыкался на трабл с пауком, но господин
А.Новодворский выручил может и Вам поможет, цитирую:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face="Arial CYR" size=2>Господа, а вот это вы читали? :<BR>atch
Description<BR>
-----------------<BR><BR>
Oracle8i for Linux is shipped with archived objects which were compiled
using<BR>
glibc-2.1.3. The executable components are then linked at install-time
using<BR>
these archives. Due to compatibility limitations in glibc, if the
target<BR>
system for an installation is based on a later version of glibc, then
the<BR>
executables produced by the linker will not be valid. As a workaround
to<BR>
this limitation, we have created a set of stub libraries which are used
at<BR>
link-time only to mimic the contents of glibc-2.1.3 shared objects.
Note<BR>
that these stub libraries do not contain valid executable code, and
therefore<BR>
*must NOT* be included in the library path searched by the dynamic
loader<BR>
(i.e., do not include $ORACLE_HOME/lib/stubs in
LD_LIBRARY_PATH).<BR><BR>
===========================================<BR>
Instructions for New Oracle8i
Installations<BR>
-------------------------------------------<BR><BR>
Install Oracle8i as usual, but choose not to create a database during
install.<BR><BR>
Once installation is complete, follow the procedure described in
the<BR>
section "Instructions for Existing Installations" below. It will
then<BR>
be possible to create a
database.<BR><BR><BR>================================================<BR>
Instructions for Existing Oracle8i
Installations<BR><BR>------------------------------------------------<BR><BR>
Place the tar file glibc-2.1.3-stubs.tar.gz in $ORACLE_HOME. Make
sure<BR>
ORACLE_HOME is set in your environment. Then carry out the following
steps:<BR><BR>
cd
$ORACLE_HOME<BR>
tar xvfz
glibc-2.1.3-stubs.tar.gz<BR>
./setup_stubs.sh<BR><BR>
You should now be able to use Oracle as
usual.<BR><BR>
================<BR>
Warning<BR>
----------------<BR><BR>
Make sure the directory $ORACLE_HOME/lib is not listed in
your<BR>
/etc/ld.so.conf. The system could potentially become unstable after
applying<BR>
this patch in that case. If $ORACLE_HOME/lib is currently listed
in<BR>
/etc/ld.so.conf, remove it and run ldconfig before applying this
patch.<BR><BR>
================================<BR>
Notes for Application
Developers<BR>
--------------------------------<BR><BR>
If your application does not require linking at install sites, then
no<BR>
additional steps are required for your application to be compatible
with<BR>
glibc or the Oracle8i client shared library after the installation of
this<BR>
patch. This is true regardless of whether your application was
compiled<BR>
using glibc-2.1.3 or a later
version.<BR><BR>
If your application is compiled using glibc-2.1.3 and requires linking
at<BR>
install-time using the Oracle8i client shared library, then you may
also<BR>
need to link your application using the stub libraries provided in
this<BR>
patch. For example, an application which might typically be linked
as<BR>
follows on a glibc-2.1.3 based
system:<BR><BR>
gcc -o app app.o -L$ORACLE_HOME/lib
-lclntsh<BR><BR>
should now be linked as follows on systems with a newer version of
glibc,<BR>
in order to ensure
compatibility:<BR><BR>
gcc -o app app.o -L$ORACLE_HOME/lib -L$ORACLE_HOME/lib/stubs
-lclntsh<BR><BR>
If your application is compiled using a version of glibc later than
2.1.3<BR>
and requires linking at install-time using the Oracle8i client
shared<BR>
library, then you must NOT link your application with the stub
libraries<BR>
provided in this patch. Doing so may either cause the link to fail or
the<BR>
resulting executables to be
invalid.<BR><BR>
Note that the stub libraries provided in this patch only cover the
shared<BR>
objects that make up glibc. If your application must be linked at
install-<BR>
time with other shared objects which were built to have dependencies on
the<BR>
locally installed version of glibc (e.g., X11), then your application
must<BR>
be compiled using the same version of glibc that was used by those
other<BR>
components. For example, on a system with glibc-2.2, linking
your<BR>
application with libX11.so will fail if you attempt to use the
glibc-2.1.3<BR>
stub libraries, since libX11.so on that system will have been compiled
and<BR>
linked using
glibc-2.2.<BR><BR>
================<BR>
Revision
History<BR>
----------------<BR><BR>
06-FEB-2001: added ldconfig warning to
README<BR>
08-FEB-2001: added libnsl.so stub needed for OPS
cm/nm<BR>
28-FEB-2001: move stub libraries from $OH/lib to
$OH/lib/stubs<BR>
01-MAR-2001: added stubs for all remaining glibc
libraries<BR>
14-MAR-2001: added setup_stubs.sh to simplify
installation<BR>
16-MAR-2001: added patch description and notes for application
developers<BR><BR>-------------<BR>URL:<BR><A
href="http://otn.oracle.com/software/products/oracle8i/files/READMEglib213.html">http://otn.oracle.com/software/products/oracle8i/files/READMEglib213.html</A></FONT></DIV></BODY></HTML>