Generic Linux Installer not seeing file within its own folde

Posts: 45
Joined: Thu Mar 08, 2012 7:19 pm

Re: Generic Linux Installer not seeing file within its own f

Post by xabre »

No need to symlink libpcre, just install luazip5.1, lrexlib-pcre, lua51, lua51-filesystem, lua51-sql-sqlite, quazip, all are in official repoes or AUR. You can't use all libraries provided with generic installer (libyajl being the only exception) as they are compiled with older version of glibc than Arch has (you'll get "version `GLIBC_2.17' not found" errors, because Arch is using glibc 2.19).
But if you install packages from official repositories it complains about, thus use system libs instead of provided ones, it will work.

Small hint: pkgfile is a very handy tool for Arch to find which package contains some specific file when something complains about it missing.

User avatar
Posts: 994
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Re: Generic Linux Installer not seeing file within its own f

Post by SlySven »

And if you want to find all the libraries that mudlet or any other executable will try to find when it starts up you might get some useful data from the ldd(1) command, this lists EVERY library it wants to use and if any are missing it will show up, for example on a development build I had to hand:

Code: Select all

stephen@Kirk:/media/spare/src/mudlet-dev/Mudlet2/verify/build-src-Desktop_Qt_5_2_1_GCC_32bit-Debug$ ldd ./mudlet =>  (0xb77db000) => /lib/i386-linux-gnu/ (0xb7776000) => /usr/lib/i386-linux-gnu/ (0xb7749000) => /usr/lib/i386-linux-gnu/ (0xb76f3000) => /usr/lib/i386-linux-gnu/ (0xb76e8000) => /usr/lib/i386-linux-gnu/ (0xb7673000) => /usr/local/lib/ (0xb765f000) => /lib/i386-linux-gnu/ (0xb7646000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb75e3000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb7507000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb6eb8000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb6d63000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb68c8000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb63fe000) => /usr/lib/i386-linux-gnu/ (0xb63a4000) => /lib/i386-linux-gnu/i686/cmov/ (0xb638b000) => /usr/lib/i386-linux-gnu/ (0xb629f000) => /lib/i386-linux-gnu/i686/cmov/ (0xb6279000) => /lib/i386-linux-gnu/ (0xb625b000) => /lib/i386-linux-gnu/i686/cmov/ (0xb60f7000) => /lib/i386-linux-gnu/i686/cmov/ (0xb60f3000) => /usr/lib/i386-linux-gnu/ (0xb60a2000) => /usr/lib/i386-linux-gnu/ (0xb6050000) => /lib/i386-linux-gnu/ (0xb5f52000) => /usr/lib/i386-linux-gnu/ (0xb5e1a000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb5bf8000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb5a7f000) => /usr/lib/i386-linux-gnu/ (0xb5a7c000) => /lib/i386-linux-gnu/i686/cmov/ (0xb5a72000)
	/lib/ (0xb77dc000) => /usr/lib/i386-linux-gnu/ (0xb5a5c000) => /usr/lib/i386-linux-gnu/ (0xb5a4a000) => /usr/lib/i386-linux-gnu/ (0xb5a47000) => /usr/lib/i386-linux-gnu/ (0xb5a41000) => /usr/lib/i386-linux-gnu/ (0xb5a3e000) => /usr/lib/i386-linux-gnu/ (0xb5a25000) => /usr/lib/i386-linux-gnu/ (0xb5a02000) => /usr/lib/i386-linux-gnu/ (0xb59fc000) => /usr/lib/i386-linux-gnu/ (0xb59ee000) => /lib/i386-linux-gnu/ (0xb59e2000) => /usr/lib/i386-linux-gnu/pulseaudio/ (0xb596f000) => /lib/i386-linux-gnu/ (0xb5924000) => /lib/i386-linux-gnu/ (0xb591f000) => /usr/lib/i386-linux-gnu/ (0xb5916000) => /media/spare/Qt/5.2.1/gcc/lib/ (0xb43cc000) => /usr/lib/i386-linux-gnu/ (0xb43c9000) => /usr/lib/i386-linux-gnu/ (0xb43c3000) => /usr/lib/i386-linux-gnu/ (0xb43aa000) => /usr/lib/i386-linux-gnu/ (0xb43a2000) => /usr/lib/i386-linux-gnu/ (0xb439b000) => /lib/i386-linux-gnu/ (0xb4391000) => /usr/lib/i386-linux-gnu/ (0xb431d000) => /usr/lib/i386-linux-gnu/ (0xb4317000) => /lib/i386-linux-gnu/ (0xb4311000) => /lib/i386-linux-gnu/ (0xb430a000) => /usr/lib/i386-linux-gnu/ (0xb42fb000) => /lib/i386-linux-gnu/i686/cmov/ (0xb42e4000) => /usr/lib/i386-linux-gnu/ (0xb4294000) => /usr/lib/i386-linux-gnu/ (0xb411c000) => /usr/lib/i386-linux-gnu/ (0xb40ef000) => /usr/lib/i386-linux-gnu/ (0xb40e8000) => /lib/i386-linux-gnu/i686/cmov/ (0xb40d4000)
Don't worry about the linux-gate entry that's a special case, but you can see every other library file it wants...!

Posts: 1
Joined: Sat Aug 23, 2014 5:36 am

Re: Generic Linux Installer not seeing file within its own f

Post by orik »

Hello Iktomi, Xabre and SlySven,

I have experienced the same problem Iktomi reported, and have successfully overcomed it.
So, I share my solution next:

Firstly, I work on a Debian distribution (wheezy). I can confirm it is a dependency problem, and a little step must be done after installing the dependencies pointed by Xabre ( luazip5.1, lrexlib-pcre, lua51, lua51-filesystem, lua51-sql-sqlite, quazip) .That is, in my case.

I only received the error:

Code: Select all

./mudlet: error while loading shared libraries: cannot open shared object file: No such file or directory
which, as Xabre pointed out, is related to the quazip package.

Now, for Debian systems, quazip is only included in the unstable (sid) release at this point. So, you need to install it bare handed. You can obtain the source code from it's source forge webpage and the instructions for the project's webpage.

However, a pair of things must be considered:

1st. As explainded in the project's site, a fundamental dependency is to have Qt installed among with it's dev files (version 4 or 5). If you don't have this packages, be sure to install them first (Welcome to the dependency hell!)

2nd. You must set the installation path to /usr or /usr/local, depending of your conf file, check it by executing:

Code: Select all

cat /etc/
Next, if the qt dependency is satisfied (an easy way to verify is simply to run the "qmake" command anywhere in a console), you should execute the following steps to install quazip:

Code: Select all

$ cd /wherever/quazip/source/is/quazip-x.y.z/quazip
$ qmake PREFIX=/usr
$ make
$ sudo make install
This will install quazip's shared libraries and include files in the /usr/lib and /usr/include directories respectively.

I found another step has to be taken for the current version of quazip. As SlySven pointed, ldd command allows you to check for shared libraries dependencies. And it so happens that Mudlet 2.1 looks a the shared library named which is no longer existent in the current version of quazip.

At this point you should verify that the libquazip files were actually installed in the /usr/lib directory. This is easily done with

Code: Select all

$ ls /usr/lib | grep -e quazip
If you have followed me this far, you are just a step away. Now, we only need to create a symbolic link
(as pointed out here):

Code: Select all

$ cd /usr/lib
$ sudo ln -s
And then you're done. You should be able to run either ./ or ./ without problems... That is, if you only missed the quazip library. In case you still have other problems, verify you have installed the dependencies pointed by Xabre.

I was able to correct the error following the exposed steps. Please let me know if this could solve your problem.

Good luck!
Orik 8-)

Post Reply