Note that there are some explanatory texts on larger screens.

plurals
  1. POlibaio.so.1: cannot open shared object file
    primarykey
    data
    text
    <p>I have a simple test program that when I run I get:</p> <pre><code>./hello: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory </code></pre> <p>I link it like this:</p> <pre><code>$(CC) $(CCFLAGS) -o hello hello.o -L../ocilib-3.9.3/src/.libs -L../instantclient_11_2 -locilib </code></pre> <p>My LD_LIBRARY_PATH contains this:</p> <pre><code>LD_LIBRARY_PATH=../ocilib-3.9.3/src/.libs:../instantclient_11_2:/usr/lib </code></pre> <p>/usr/lib looks like this:</p> <pre><code>Linux$ ls -l /usr/lib/libaio* lrwxrwxrwx 1 root root 15 Nov 5 2008 /usr/lib/libaio.so.1 -&gt; libaio.so.1.0.1 -rwxr-xr-x 1 root root 2632 Sep 16 2005 /usr/lib/libaio.so.1.0.0 -rwxr-xr-x 1 root root 2628 Sep 16 2005 /usr/lib/libaio.so.1.0.1 </code></pre> <p>Output of ldd hello:</p> <pre><code>libocilib.so.3 =&gt; ../ocilib-3.9.3/src/.libs/libocilib.so.3 (0x0000002a95558000) libc.so.6 =&gt; /lib64/tls/libc.so.6 (0x0000003811200000) libclntsh.so.11.1 =&gt; ../instantclient_11_2/libclntsh.so.11.1 (0x0000002a956c4000) /lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000) libnnz11.so =&gt; ../instantclient_11_2/libnnz11.so (0x0000002a97f56000) libdl.so.2 =&gt; /lib64/libdl.so.2 (0x0000003811500000) libm.so.6 =&gt; /lib64/tls/libm.so.6 (0x0000003811700000) libpthread.so.0 =&gt; /lib64/tls/libpthread.so.0 (0x0000003811b00000) libnsl.so.1 =&gt; /lib64/libnsl.so.1 (0x0000003819000000) libaio.so.1 =&gt; not found </code></pre> <p>I'm hoping that I'm missing something simple here. The oracle instantclient package appears to require libaio, but that seems to be installed already so what's the problem?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload