Ubuntu 12.04 - slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory #16

francisluong · 2013-09-25T16:23:07Z

Hi Guys,

I am having some trouble with building libslax. On CENTOS, I couldn't get a new enough version of libcurl. On Ubuntu 12.04, I can build it but I can't open the shared object.

fluong@ubuntu:/Downloads/libslax-0.17.1$ which slaxproc
/usr/local/bin/slaxproc
fluong@ubuntu:/Downloads/libslax-0.17.1$ slaxproc --versin
slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory
fluong@ubuntu:/Downloads/libslax-0.17.1$ ls /usr/local/lib
libjuise.a libjuise.so libjuise.so.0.0.0 libslax.la libslax.so.0 pkgconfig slax
libjuise.la libjuise.so.0 libslax.a libslax.so libslax.so.0.0.0 python2.7
fluong@ubuntu:/Downloads/libslax-0.17.1$

I could use some help or suggestions.

Thanks,

Franco

philshafer · 2013-09-25T19:02:49Z

On Sep 25, 2013, at 12:23 PM, francisluong wrote:

I am having some trouble with building libslax. On CENTOS, I couldn't get a new enough version of libcurl.

What packaging scheme does CENTOS use? I know we use CENTOS for junospace and it runs libslax and juise.

On Ubuntu 12.04, I can build it but I can't open the shared object.

fluong@ubuntu:/Downloads/libslax-0.17.1$ slaxproc --versin
slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory
fluong@ubuntu:/Downloads/libslax-0.17.1$ ls /usr/local/lib
libjuise.a libjuise.so libjuise.so.0.0.0 libslax.la libslax.so.0 pkgconfig slax
libjuise.la libjuise.so.0 libslax.a libslax.so libslax.so.0.0.0 python2.7

What this installed from the RPM? The files should be in /usr/lib64. "ldd" should be able to tell you which libs it needs:

[root@localhost vagrant]# ldd /usr/bin/slaxproc
linux-vdso.so.1 => (0x00007fff1757c000)
libslax.so.0 => /usr/lib64/libslax.so.0 (0x00007fcd2b73e000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007fcd2b379000)
libxslt.so.1 => /usr/lib64/libxslt.so.1 (0x00007fcd2b13a000)
librt.so.1 => /usr/lib64/librt.so.1 (0x00007fcd2af32000)
libexslt.so.0 => /usr/lib64/libexslt.so.0 (0x00007fcd2ad1d000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007fcd2a9b7000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007fcd2a7a1000)
libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007fcd2a59d000)
libm.so.6 => /usr/lib64/libm.so.6 (0x00007fcd2a29b000)
libc.so.6 => /usr/lib64/libc.so.6 (0x00007fcd29ee3000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fcd29ccd000)
libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007fcd29ab0000)
/lib64/ld-linux-x86-64.so.2 (0x00007fcd2b986000)
libgcrypt.so.11 => /usr/lib64/libgcrypt.so.11 (0x00007fcd29837000)
libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007fcd29633000)
liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007fcd2940d000)

What does your ldd say?

Thanks,
Phil

francisluong · 2013-09-25T19:33:23Z

Phil,

Thanks for the reply. Please find my responses below. I was able to get it
working on Ubuntu. No joy on Centos 6.4 just yet. I only need one but
I'll gladly help pitch in to work out kinks.

-Franco

Centos

What packaging scheme does CENTOS use? I know we use CENTOS for junospace

and it runs libslax and juise.

If I understand your question, Centos uses yum/rpm. I can't seem to get it
built/installed here.

Attempting to build using the .tar.gz I get:

checking for libcurl libraries >= 7.21.3... configure: error: Version
libcurl 7.19.7 found. You need at least libcurl 7.21.3 for this version of
libslax

Using the RPM, I get this:

Error: Package: libslax-0.17.1-1.fc18.x86_64

(/libslax-0.17.1-1.fc18.x86_64)
Requires: libc.so.6(GLIBC_2.14)(64bit)

[fluong@fxcentosvmw Downloads]$ yum list installed glibc
Installed Packages
glibc.i686 2.12-1.107.el6_4.4 @updates
glibc.x86_64 2.12-1.107.el6_4.4 @updates

_[fluong@fxcentosvmw Downloads]$ cat /etc/_release**
CentOS release 6.4 (Final)
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
cat: /etc/lsb-release.d: Is a directory
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA

Ubuntu

What does your ldd say?

For Ubuntu, I built it using the .tar.gz file.

*fluong@ubuntu:~/Downloads/libslax-0.17.1$ ldd /usr/local/bin/slaxproc *
linux-vdso.so.1 => (0x00007fff784c5000)
libslax.so.0 => not found
libxslt.so.1 => /usr/lib/x86_64-linux-gnu/libxslt.so.1
(0x00007ff84d7f8000)
libexslt.so.0 => /usr/lib/x86_64-linux-gnu/libexslt.so.0
(0x00007ff84d5e2000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2
(0x00007ff84d286000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff84cec7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff84cbca000)
libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11
(0x00007ff84c94c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff84c748000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ff84c530000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff84da48000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x00007ff84c32c000)

I was able to get it working here by symlink-ing the shared object
into /usr/lib/x86_64-linux-gnu/

fluong@ubuntu:~$ cd /usr/lib/x86_64-linux-gnu/

fluong@ubuntu:/usr/lib/x86_64-linux-gnu$ sudo ln -s
/usr/local/lib/libslax.so.0
[sudo] password for fluong:

fluong@ubuntu:/usr/lib/x86_64-linux-gnu$ slaxproc --version
libslax version 0.17.1
Using libxml 20708, libxslt 10126 and libexslt 815
slaxproc was compiled against libxml 20708, libxslt 10126 and libexslt 815
libxslt 10126 was compiled against libxml 20708
libexslt 815 was compiled against libxml 20708
fluong@ubuntu:/usr/lib/x86_64-linux-gnu$

philshafer · 2013-09-25T19:56:41Z

On Sep 25, 2013, at 3:33 PM, francisluong wrote:

For Ubuntu, I built it using the .tar.gz file.

Hmmm... does your "make install" give any errors? You should see something like:

Making install in libslax
../../install-sh -c -d '/Users/phil/work/root/lib'
glibtool --mode=install /usr/bin/install -c libslax.la '/Users/phil/work/root/lib'
glibtool: install: /usr/bin/install -c .libs/libslax.0.dylib /Users/phil/work/root/lib/libslax.0.dylib
glibtool: install: (cd /Users/phil/work/root/lib && { ln -s -f libslax.0.dylib libslax.dylib || { rm -f libslax.dylib && ln -s libslax.0.dylib libslax.dylib; }; })
glibtool: install: /usr/bin/install -c .libs/libslax.lai /Users/phil/work/root/lib/libslax.la
glibtool: install: /usr/bin/install -c .libs/libslax.a /Users/phil/work/root/lib/libslax.a
glibtool: install: chmod 644 /Users/phil/work/root/lib/libslax.a
glibtool: install: ranlib /Users/phil/work/root/lib/libslax.a
../../install-sh -c -d '/Users/phil/work/root/share/man/man3'
/usr/bin/install -c -m 644 ../../libslax/libslax.3x '/Users/phil/work/root/share/man/man3'
../../install-sh -c -d '/Users/phil/work/root/include/libslax'
/usr/bin/install -c -m 644 ../../libslax/slax.h slaxconfig.h ../../libslax/slaxdata.h ../../libslax/slaxdyn.h ../../libslax/xmlsoft.h '/Users/phil/work/root/include/libslax'
...

I'm downloading vagrant boxes for centos-6.4 and ubuntu-12.1, but it will likely be tomorrow before I get a chance to play with them.

Thanks,
Phil

francisluong · 2013-09-25T20:42:04Z

Pardon the long output. It looks like libtool has some textblocks messages
about LIBDIR. It's a bit beyond my comprehension.

-Franco

fluong@ubuntu:~/Downloads/libslax-0.17.1/build$ sudo make install
[sudo] password for fluong:
Making install in libslax
make[1]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/libslax' BISON slaxparser.h CC jsonlexer.lo CC jsonwriter.lo CC slaxdebugger.lo CC slaxdyn.lo CC slaxext.lo CC slaxio.lo CC slaxlexer.lo CC slaxloader.lo CC slaxmvar.lo CC slaxparser.lo CC slaxprofiler.lo CC slaxstring.lo CC slaxtree.lo CC slaxwriter.lo CCLD libslax.la make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/libslax'
BISON slaxparser.h
CC jsonlexer.lo
CC jsonwriter.lo
CC slaxdebugger.lo
CC slaxdyn.lo
CC slaxext.lo
CC slaxio.lo
CC slaxlexer.lo
CC slaxloader.lo
CC slaxmvar.lo
CC slaxparser.lo
CC slaxprofiler.lo
CC slaxstring.lo
CC slaxtree.lo
CC slaxwriter.lo
CCLD libslax.la
/bin/mkdir -p '/usr/local/lib'
/bin/bash ../libtool --mode=install /usr/bin/install -c
libslax.la'/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libslax.so.0.0.0
/usr/local/lib/libslax.so.0.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libslax.so.0.0.0
libslax.so.0 || { rm -f libslax.so.0 && ln -s libslax.so.0.0.0
libslax.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libslax.so.0.0.0
libslax.so || { rm -f libslax.so && ln -s libslax.so.0.0.0 libslax.so; }; })
libtool: install: /usr/bin/install -c .libs/libslax.lai /usr/local/lib/
libslax.la
libtool: install: /usr/bin/install -c .libs/libslax.a
/usr/local/lib/libslax.a
libtool: install: chmod 644 /usr/local/lib/libslax.a
libtool: install: ranlib /usr/local/lib/libslax.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib

Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

/bin/mkdir -p '/usr/local/share/man/man3'
/usr/bin/install -c -m 644 ../../libslax/libslax.3x
'/usr/local/share/man/man3'
/bin/mkdir -p '/usr/local/include/libslax'
/usr/bin/install -c -m 644 ../../libslax/slax.h slaxconfig.h
../../libslax/slaxdata.h ../../libslax/slaxdyn.h ../../libslax/xmlsoft.h
'/usr/local/include/libslax'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/libslax' make[1]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/libslax'
Making install in extensions
make[1]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions' Making install in bit make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/bit'
make[3]: Entering directory
`/home/fluong/Downloads/libslax-0.17.1/build/extensions/bit'
/bin/mkdir -p '/usr/local/lib/slax/extensions'
/bin/bash ../../libtool --mode=install /usr/bin/install -c
libext_bit.la '/usr/local/lib/slax/extensions'
libtool: install: /usr/bin/install -c .libs/libext_bit.so.0.0.0
/usr/local/lib/slax/extensions/libext_bit.so.0.0.0
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_bit.so.0.0.0 libext_bit.so.0 || { rm -f libext_bit.so.0 && ln -s
libext_bit.so.0.0.0 libext_bit.so.0; }; })
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_bit.so.0.0.0 libext_bit.so || { rm -f libext_bit.so && ln -s
libext_bit.so.0.0.0 libext_bit.so; }; })
libtool: install: /usr/bin/install -c .libs/libext_bit.lai
/usr/local/lib/slax/extensions/libext_bit.la
libtool: install: /usr/bin/install -c .libs/libext_bit.a
/usr/local/lib/slax/extensions/libext_bit.a
libtool: install: chmod 644 /usr/local/lib/slax/extensions/libext_bit.a
libtool: install: ranlib /usr/local/lib/slax/extensions/libext_bit.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib/slax/extensions

Libraries have been installed in:
/usr/local/lib/slax/extensions

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

make install-exec-hook
make[4]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/bit' Install link libext_bit.so.0 -> bit.prefix:http%3A%2F%2Fxml.libslax.org%2Fbit.ext ... make[4]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/bit'
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/bit'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/bit' Making install in curl make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/curl'
make[3]: Entering directory
`/home/fluong/Downloads/libslax-0.17.1/build/extensions/curl'
/bin/mkdir -p '/usr/local/lib/slax/extensions'
/bin/bash ../../libtool --mode=install /usr/bin/install -c
libext_curl.la '/usr/local/lib/slax/extensions'
libtool: install: /usr/bin/install -c .libs/libext_curl.so.0.0.0
/usr/local/lib/slax/extensions/libext_curl.so.0.0.0
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_curl.so.0.0.0 libext_curl.so.0 || { rm -f libext_curl.so.0 && ln -s
libext_curl.so.0.0.0 libext_curl.so.0; }; })
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_curl.so.0.0.0 libext_curl.so || { rm -f libext_curl.so && ln -s
libext_curl.so.0.0.0 libext_curl.so; }; })
libtool: install: /usr/bin/install -c .libs/libext_curl.lai
/usr/local/lib/slax/extensions/libext_curl.la
libtool: install: /usr/bin/install -c .libs/libext_curl.a
/usr/local/lib/slax/extensions/libext_curl.a
libtool: install: chmod 644 /usr/local/lib/slax/extensions/libext_curl.a
libtool: install: ranlib /usr/local/lib/slax/extensions/libext_curl.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib/slax/extensions

Libraries have been installed in:
/usr/local/lib/slax/extensions

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

make install-exec-hook
make[4]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/curl' Install link libext_curl.so.0 -> curl.prefix:http%3A%2F%2Fxml.libslax.org%2Fcurl.ext ... make[4]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/curl'
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/curl'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/curl' Making install in exslt make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt'
make[3]: Entering directory
`/home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt'
/bin/mkdir -p '/usr/local/lib/slax/extensions'
/bin/bash ../../libtool --mode=install /usr/bin/install -c
libext_exslt.la '/usr/local/lib/slax/extensions'
libtool: install: /usr/bin/install -c .libs/libext_exslt.so.0.0.0
/usr/local/lib/slax/extensions/libext_exslt.so.0.0.0
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_exslt.so.0.0.0 libext_exslt.so.0 || { rm -f libext_exslt.so.0 && ln
-s libext_exslt.so.0.0.0 libext_exslt.so.0; }; })
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_exslt.so.0.0.0 libext_exslt.so || { rm -f libext_exslt.so && ln -s
libext_exslt.so.0.0.0 libext_exslt.so; }; })
libtool: install: /usr/bin/install -c .libs/libext_exslt.lai
/usr/local/lib/slax/extensions/libext_exslt.la
libtool: install: /usr/bin/install -c .libs/libext_exslt.a
/usr/local/lib/slax/extensions/libext_exslt.a
libtool: install: chmod 644 /usr/local/lib/slax/extensions/libext_exslt.a
libtool: install: ranlib /usr/local/lib/slax/extensions/libext_exslt.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib/slax/extensions

Libraries have been installed in:
/usr/local/lib/slax/extensions

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

make install-exec-hook
make[4]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt' Install link libext_exslt.so.0 -> ... make[4]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt'
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/exslt' Making install in os make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/os'
make[3]: Entering directory
`/home/fluong/Downloads/libslax-0.17.1/build/extensions/os'
/bin/mkdir -p '/usr/local/lib/slax/extensions'
/bin/bash ../../libtool --mode=install /usr/bin/install -c
libext_os.la'/usr/local/lib/slax/extensions'
libtool: install: /usr/bin/install -c .libs/libext_os.so.0.0.0
/usr/local/lib/slax/extensions/libext_os.so.0.0.0
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_os.so.0.0.0 libext_os.so.0 || { rm -f libext_os.so.0 && ln -s
libext_os.so.0.0.0 libext_os.so.0; }; })
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_os.so.0.0.0 libext_os.so || { rm -f libext_os.so && ln -s
libext_os.so.0.0.0 libext_os.so; }; })
libtool: install: /usr/bin/install -c .libs/libext_os.lai
/usr/local/lib/slax/extensions/libext_os.la
libtool: install: /usr/bin/install -c .libs/libext_os.a
/usr/local/lib/slax/extensions/libext_os.a
libtool: install: chmod 644 /usr/local/lib/slax/extensions/libext_os.a
libtool: install: ranlib /usr/local/lib/slax/extensions/libext_os.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib/slax/extensions

Libraries have been installed in:
/usr/local/lib/slax/extensions

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

make install-exec-hook
make[4]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/os' Install link libext_os.so.0 -> os.prefix:http%3A%2F%2Fxml.libslax.org%2Fos.ext ... make[4]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/os'
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/os'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/os' Making install in xutil make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil'
make[3]: Entering directory
`/home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil'
/bin/mkdir -p '/usr/local/lib/slax/extensions'
/bin/bash ../../libtool --mode=install /usr/bin/install -c
libext_xutil.la '/usr/local/lib/slax/extensions'
libtool: install: /usr/bin/install -c .libs/libext_xutil.so.0.0.0
/usr/local/lib/slax/extensions/libext_xutil.so.0.0.0
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_xutil.so.0.0.0 libext_xutil.so.0 || { rm -f libext_xutil.so.0 && ln
-s libext_xutil.so.0.0.0 libext_xutil.so.0; }; })
libtool: install: (cd /usr/local/lib/slax/extensions && { ln -s -f
libext_xutil.so.0.0.0 libext_xutil.so || { rm -f libext_xutil.so && ln -s
libext_xutil.so.0.0.0 libext_xutil.so; }; })
libtool: install: /usr/bin/install -c .libs/libext_xutil.lai
/usr/local/lib/slax/extensions/libext_xutil.la
libtool: install: /usr/bin/install -c .libs/libext_xutil.a
/usr/local/lib/slax/extensions/libext_xutil.a
libtool: install: chmod 644 /usr/local/lib/slax/extensions/libext_xutil.a
libtool: install: ranlib /usr/local/lib/slax/extensions/libext_xutil.a
libtool: finish:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin"

ldconfig -n /usr/local/lib/slax/extensions

Libraries have been installed in:
/usr/local/lib/slax/extensions

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
use the `-Wl,-rpath -Wl,LIBDIR' linker flag
have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for

more information, such as the ld(1) and ld.so(8) manual pages.

make install-exec-hook
make[4]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil' Install link libext_xutil.so.0 -> xutil.prefix:http%3A%2F%2Fxml.libslax.org%2Fxutil.ext ... make[4]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil'
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions/xutil' make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/extensions'
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions' make[3]: Nothing to be done forinstall-exec-am'.
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/extensions' make[1]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/extensions'
Making install in slaxproc
make[1]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/slaxproc' CCLD slaxproc make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/slaxproc'
/bin/mkdir -p '/usr/local/bin'
/bin/bash ../libtool --mode=install /usr/bin/install -c slaxproc
'/usr/local/bin'
libtool: install: /usr/bin/install -c .libs/slaxproc /usr/local/bin/slaxproc
/bin/mkdir -p '/usr/local/share/man/man1'
/usr/bin/install -c -m 644 ../../slaxproc/slaxproc.1x
../../slaxproc/slaxdebugger.1x '/usr/local/share/man/man1'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/slaxproc' make[1]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/slaxproc'
Making install in tests
make[1]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/tests' Making install in core make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/tests/core'
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/core' make[3]: Nothing to be done forinstall-exec-am'.
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/tests/core'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/core' Making install in bugs make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/tests/bugs'
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/bugs' make[3]: Nothing to be done forinstall-exec-am'.
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/tests/bugs'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/bugs' Making install in errors make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/tests/errors'
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/errors' make[3]: Nothing to be done forinstall-exec-am'.
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/tests/errors'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/tests/errors' make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/tests'
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/tests' make[3]: Nothing to be done forinstall-exec-am'.
make[3]: Nothing to be done for install-data-am'. make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/tests'
make[2]: Leaving directory
/home/fluong/Downloads/libslax-0.17.1/build/tests' make[1]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/tests'
Making install in doc
make[1]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/doc' make[2]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/doc'
make[2]: Nothing to be done for install-exec-am'. make install-data-hook make[3]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/doc'
Installing oxtradoc ...
make[3]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/doc' make[2]: Leaving directory/home/fluong/Downloads/libslax-0.17.1/build/doc'
make[1]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/doc' Making install in bin make[1]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build/bin'
make[2]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/bin' make[2]: Nothing to be done forinstall-exec-am'.
make install-data-hook
make[3]: Entering directory
/home/fluong/Downloads/libslax-0.17.1/build/bin' Installing gt ... make[3]: Leaving directory/home/fluong/Downloads/libslax-0.17.1/build/bin'
make[2]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build/bin' make[1]: Leaving directory/home/fluong/Downloads/libslax-0.17.1/build/bin'
make[1]: Entering directory /home/fluong/Downloads/libslax-0.17.1/build' make[2]: Entering directory/home/fluong/Downloads/libslax-0.17.1/build'
/bin/mkdir -p '/usr/local/bin'
/usr/bin/install -c slax-config '/usr/local/bin'
/bin/mkdir -p '/usr/local/share/doc/libslax'
/usr/bin/install -c -m 644 ../Copyright ../doc/slax.txt
'/usr/local/share/doc/libslax'
/bin/mkdir -p '/usr/local/lib/pkgconfig'
/usr/bin/install -c -m 644 packaging/libslax.pc '/usr/local/lib/pkgconfig'
make[2]: Leaving directory /home/fluong/Downloads/libslax-0.17.1/build' make[1]: Leaving directory/home/fluong/Downloads/libslax-0.17.1/build'
fluong@ubuntu:~/Downloads/libslax-0.17.1/build$

=== Francis Luong (Franco)
=== http://about.me/francisluong

=== http://about.me/francoonthebass

On Wed, Sep 25, 2013 at 3:56 PM, Phil Shafer [email protected]:

On Sep 25, 2013, at 3:33 PM, francisluong wrote:

For Ubuntu, I built it using the .tar.gz file.

Hmmm... does your "make install" give any errors? You should see something
like:

Making install in libslax
../../install-sh -c -d '/Users/phil/work/root/lib'
glibtool --mode=install /usr/bin/install -c libslax.la'/Users/phil/work/root/lib'
glibtool: install: /usr/bin/install -c .libs/libslax.0.dylib
/Users/phil/work/root/lib/libslax.0.dylib
glibtool: install: (cd /Users/phil/work/root/lib && { ln -s -f
libslax.0.dylib libslax.dylib || { rm -f libslax.dylib && ln -s
libslax.0.dylib libslax.dylib; }; })
glibtool: install: /usr/bin/install -c .libs/libslax.lai
/Users/phil/work/root/lib/libslax.la
glibtool: install: /usr/bin/install -c .libs/libslax.a
/Users/phil/work/root/lib/libslax.a
glibtool: install: chmod 644 /Users/phil/work/root/lib/libslax.a
glibtool: install: ranlib /Users/phil/work/root/lib/libslax.a
../../install-sh -c -d '/Users/phil/work/root/share/man/man3'
/usr/bin/install -c -m 644 ../../libslax/libslax.3x
'/Users/phil/work/root/share/man/man3'
../../install-sh -c -d '/Users/phil/work/root/include/libslax'
/usr/bin/install -c -m 644 ../../libslax/slax.h slaxconfig.h
../../libslax/slaxdata.h ../../libslax/slaxdyn.h ../../libslax/xmlsoft.h
'/Users/phil/work/root/include/libslax'
...

I'm downloading vagrant boxes for centos-6.4 and ubuntu-12.1, but it will
likely be tomorrow before I get a chance to play with them.

Thanks,
Phil

�
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-25119454
.

philshafer · 2013-09-25T21:17:17Z

On Sep 25, 2013, at 4:39 PM, francisluong wrote:

/bin/bash ../libtool --mode=install /usr/bin/install -c libslax.la '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libslax.so.0.0.0 /usr/local/lib/libslax.so.0.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libslax.so.0.0.0 libslax.so.0 || { rm -f libslax.so.0 && ln -s libslax.so.0.0.0 libslax.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libslax.so.0.0.0 libslax.so || { rm -f libslax.so && ln -s libslax.so.0.0.0 libslax.so; }; })
libtool: install: /usr/bin/install -c .libs/libslax.lai /usr/local/lib/libslax.la
libtool: install: /usr/bin/install -c .libs/libslax.a /usr/local/lib/libslax.a

These are the important lines, and they say that the symlinks should have been made.

ln -s libslax.so.0.0.0 libslax.so.0;

Not sure why it didn't work.

When you make this symlink by hand, does ldd report sane results?

Thanks,
Phil

philshafer · 2013-09-25T21:22:21Z

On Sep 25, 2013, at 4:42 PM, francisluong wrote:

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution

add LIBDIR to the `LD_RUN_PATH' environment variable
during linking

use the `-Wl,-rpath -Wl,LIBDIR' linker flag

have your system administrator add LIBDIR to `/etc/ld.so.conf'

Does ubuntu not put /usr/local/lib in /etc/ld.so.conf? The RPM installs into /usr, not /usr/local, and I'm not sure that the autotools understand the linux /usr/lib64/ concept.

You could try "../configure --prefix /usr --libdir=/usr/lib64". I'll give this a try tomorrow.

Thanks,
Phil

francisluong · 2013-09-25T21:50:02Z

I'm relatively new to Ubuntu so I'm not sure I'm going to accurately
represent it... that being said, I am not sure that Ubuntu follows the
convention of having a /usr/lib64 folder:

fluong@ubuntu:~$ ls /usr/lib64
ls: cannot access /usr/lib64: No such file or directory

See also:
http://unix.stackexchange.com/questions/43190/where-did-usr-lib64-go-and-what-is-usr-lib-x86-64-linux-gnu

=== Francis Luong (Franco)
=== http://about.me/francisluong

=== http://about.me/francoonthebass

On Wed, Sep 25, 2013 at 5:22 PM, Phil Shafer [email protected]:

On Sep 25, 2013, at 4:42 PM, francisluong wrote:

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:

add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution

add LIBDIR to the `LD_RUN_PATH' environment variable
during linking

use the `-Wl,-rpath -Wl,LIBDIR' linker flag

have your system administrator add LIBDIR to `/etc/ld.so.conf'

Does ubuntu not put /usr/local/lib in /etc/ld.so.conf? The RPM installs
into /usr, not /usr/local, and I'm not sure that the autotools understand
the linux /usr/lib64/ concept.

You could try "../configure --prefix /usr --libdir=/usr/lib64". I'll give
this a try tomorrow.

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-25125950
.

francisluong · 2013-09-25T22:22:21Z

https://wiki.debian.org/Multiarch/TheCaseForMultiarch#Proposed_Solution

philshafer · 2013-09-26T03:33:27Z

On Sep 25, 2013, at 5:50 PM, francisluong wrote:

I'm relatively new to Ubuntu so I'm not sure I'm going to accurately
represent it... that being said, I am not sure that Ubuntu follows the
convention of having a /usr/lib64 folder:

fluong@ubuntu:~$ ls /usr/lib64
ls: cannot access /usr/lib64: No such file or directory

See also:
http://unix.stackexchange.com/questions/43190/where-did-usr-lib64-go-and-what-is-usr-lib-x86-64-linux-gnu

Isn't linux a strange world!

So is /usr/local/lib in /etc/ld.so.conf?

Thanks,
Phil

francisluong · 2013-09-26T14:19:26Z

So is /usr/local/lib in /etc/ld.so.conf?

confirmed.

fluong@ubuntu:~$ cat /etc/ld.so.conf
include /etc/ld.so.conf.d/*.conf

fluong@ubuntu:/etc/ld.so.conf.d$ ls -al
total 20
drwxr-xr-x 2 root root 4096 Sep 25 05:48 .
drwxr-xr-x 121 root root 4096 Sep 25 07:54 ..
-rw-r--r-- 1 root root 44 Apr 19 2012 libc.conf
-rw-r--r-- 1 root root 276 Sep 25 05:48 vmware-tools-libraries.conf
-rw-r--r-- 1 root root 68 Apr 19 2012 x86_64-linux-gnu.conf
lrwxrwxrwx 1 root root 42 Sep 25 05:44 x86_64-linux-gnu_GL.conf ->
/etc/alternatives/x86_64-linux-gnu_gl_conf

fluong@ubuntu:/etc/ld.so.conf.d$ cat libc.conf

libc default configuration

/usr/local/lib

fluong@ubuntu:/etc/ld.so.conf.d$ cat x86_64-linux-gnu.conf

Multiarch support

/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu

philshafer · 2013-10-24T19:57:38Z

What if you use "--libdir=/usr/lib/x86_64-linux-gnu" as a configure option? That should put the .so files in the right place.

Thanks,
Phil

philshafer · 2013-10-29T14:04:53Z

I have had no success in getting one of the vagrant images up and running for ubuntu-12.04. Could you please try to above work-around and see if it works?

Thanks,
Phil

francisluong · 2013-10-29T19:52:39Z

Will do. I am OOO until oct 31. Will check then.

On Tuesday, October 29, 2013, Phil Shafer wrote:

I have had no success in getting one of the vagrant images up and running
for ubuntu-12.04. Could you please try to above work-around and see if it
works?

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-27305045
.

Sent from my Mobile

francisluong · 2013-10-31T10:00:03Z

Phil,

I was able to confirm that it worked when I:

started with my hacked symlink ubuntu
unlink the shared object in /usr/local/lib/libslax.so.0
re-run the compile with "../configure --libdir=/usr/lib/x86_64-*
linux-gnu*".

If I can reconfirm with a fresh installation, I will follow-up with
additional reply.

fluong@ubuntu:~/Downloads/libslax-0.17.1/build$ slaxproc --version
libslax version 0.17.1
Using libxml 20708, libxslt 10126 and libexslt 815
slaxproc was compiled against libxml 20708, libxslt 10126 and libexslt 815
libxslt 10126 was compiled against libxml 20708
libexslt 815 was compiled against libxml 20708

fluong@ubuntu:~/Downloads/libslax-0.17.1/build$ date
Thu Oct 31 02:59:49 PDT 2013

=== Francis Luong (Franco)
=== http://about.me/francisluong

=== http://about.me/francoonthebass

On Tue, Oct 29, 2013 at 10:04 AM, Phil Shafer [email protected]:

I have had no success in getting one of the vagrant images up and running
for ubuntu-12.04. Could you please try to above work-around and see if it
works?

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-27305045
.

philshafer · 2013-10-31T14:00:10Z

On Oct 31, 2013, at 6:00 AM, francisluong wrote:

If I can reconfirm with a fresh installation, I will follow-up with additional reply.

Can you also check the output of "ldd which slaxproc"? I'm assuming ubuntu has ldd or "otool -L" to list which libraries will be loaded:

% ldd ~/work/root/bin/slaxproc
/Users/phil/work/root/bin/slaxproc:
/Users/phil/work/root/lib/libslax.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/Users/phil/work/root/lib/libexslt.0.dylib (compatibility version 9.0.0, current version 9.17.0)
/Users/phil/work/root/lib/libxslt.1.dylib (compatibility version 3.0.0, current version 3.28.0)
/opt/local/lib/libgcrypt.11.dylib (compatibility version 20.0.0, current version 20.2.0)
/opt/local/lib/libgpg-error.0.dylib (compatibility version 11.0.0, current version 11.0.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.2.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11)
/Users/phil/work/root/lib/libxml2.2.dylib (compatibility version 12.0.0, current version 12.0.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)
/opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0)
/opt/local/lib/libreadline.6.2.dylib (compatibility version 6.0.0, current version 6.2.0)

Thanks,
Phil

francisluong · 2013-10-31T16:46:04Z

fluong@ubuntu:~/Downloads/libslax-0.17.1/build$ which slaxproc
/usr/local/bin/slaxproc

fluong@ubuntu:~/Downloads/libslax-0.17.1/build$ ldd /usr/local/bin/slaxproc
linux-vdso.so.1 => (0x00007fffe8742000)
libslax.so.0 => /usr/lib/x86_64-linux-gnu/libslax.so.0
(0x00007f5bd0ef4000)
libxslt.so.1 => /usr/lib/x86_64-linux-gnu/libxslt.so.1
(0x00007f5bd0cb8000)
libexslt.so.0 => /usr/lib/x86_64-linux-gnu/libexslt.so.0
(0x00007f5bd0aa2000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2
(0x00007f5bd0746000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5bd0387000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5bd0182000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5bcfe86000)
libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11
(0x00007f5bcfc08000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f5bcf9f0000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5bd114f000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x00007f5bcf7ec000)

=== Francis Luong (Franco)
=== http://about.me/francisluong

=== http://about.me/francoonthebass

On Thu, Oct 31, 2013 at 10:00 AM, Phil Shafer [email protected]:

On Oct 31, 2013, at 6:00 AM, francisluong wrote:

If I can reconfirm with a fresh installation, I will follow-up with
additional reply.

Can you also check the output of "ldd which slaxproc"? I'm assuming
ubuntu has ldd or "otool -L" to list which libraries will be loaded:

% ldd ~/work/root/bin/slaxproc
/Users/phil/work/root/bin/slaxproc:
/Users/phil/work/root/lib/libslax.0.dylib (compatibility version 1.0.0,
current version 1.0.0)
/opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/Users/phil/work/root/lib/libexslt.0.dylib (compatibility version 9.0.0,
current version 9.17.0)
/Users/phil/work/root/lib/libxslt.1.dylib (compatibility version 3.0.0,
current version 3.28.0)
/opt/local/lib/libgcrypt.11.dylib (compatibility version 20.0.0, current
version 20.2.0)
/opt/local/lib/libgpg-error.0.dylib (compatibility version 11.0.0, current
version 11.0.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current
version 10.2.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
125.2.11)
/Users/phil/work/root/lib/libxml2.2.dylib (compatibility version 12.0.0,
current version 12.0.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version
1.2.8)
/opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current
version 8.1.0)
/opt/local/lib/libreadline.6.2.dylib (compatibility version 6.0.0, current
version 6.2.0)

Thanks,
Phil

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-27487614
.

punisherVX · 2014-04-02T00:22:26Z

Franco/Phil -
Thanks for the thread. I ran into the exact same problem(s) in CentOS and Ubuntu. I got the Ubuntu version working using the configure --lib= setting in LinuxMint16

Edward

pklimai · 2015-11-03T17:40:20Z

+1 thanks.
This option during libslax installation heleped me on (k)ubuntu 14:
../configure --libdir=/usr/lib/i386-linux-gnu

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ubuntu 12.04 - slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory #16

Ubuntu 12.04 - slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory #16

francisluong commented Sep 25, 2013

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

philshafer commented Sep 25, 2013

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

francisluong commented Sep 25, 2013

philshafer commented Sep 26, 2013

francisluong commented Sep 26, 2013

philshafer commented Oct 24, 2013

philshafer commented Oct 29, 2013

francisluong commented Oct 29, 2013

francisluong commented Oct 31, 2013

philshafer commented Oct 31, 2013

francisluong commented Oct 31, 2013

punisherVX commented Apr 2, 2014

pklimai commented Nov 3, 2015

Ubuntu 12.04 - slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory #16

Ubuntu 12.04 - slaxproc: error while loading shared libraries: libslax.so.0: cannot open shared object file: No such file or directory #16

Comments

francisluong commented Sep 25, 2013

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

Centos

Attempting to build using the .tar.gz I get:

Using the RPM, I get this:

Ubuntu

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

ldconfig -n /usr/local/lib

more information, such as the ld(1) and ld.so(8) manual pages.

ldconfig -n /usr/local/lib/slax/extensions

more information, such as the ld(1) and ld.so(8) manual pages.

ldconfig -n /usr/local/lib/slax/extensions

more information, such as the ld(1) and ld.so(8) manual pages.

ldconfig -n /usr/local/lib/slax/extensions

more information, such as the ld(1) and ld.so(8) manual pages.

ldconfig -n /usr/local/lib/slax/extensions

more information, such as the ld(1) and ld.so(8) manual pages.

ldconfig -n /usr/local/lib/slax/extensions

more information, such as the ld(1) and ld.so(8) manual pages.

=== http://about.me/francoonthebass

philshafer commented Sep 25, 2013

philshafer commented Sep 25, 2013

francisluong commented Sep 25, 2013

=== http://about.me/francoonthebass

francisluong commented Sep 25, 2013

philshafer commented Sep 26, 2013

francisluong commented Sep 26, 2013

libc default configuration

Multiarch support

philshafer commented Oct 24, 2013

philshafer commented Oct 29, 2013

francisluong commented Oct 29, 2013

francisluong commented Oct 31, 2013

=== http://about.me/francoonthebass

philshafer commented Oct 31, 2013

francisluong commented Oct 31, 2013

=== http://about.me/francoonthebass

punisherVX commented Apr 2, 2014

pklimai commented Nov 3, 2015