#12 After compiling mlterm on openSUSE Leap 42.2, it doesn't run

[Antoine J. Mechelynck]

I tried the following in openSUSE Leap 42.2 x86_64:

1. Make sure packages fribidi and fribidi-devel are installed
2. Download the .tar.gz for mlterm 3.8.0
   The rest was done in bash running in konsole:
3. tar -zxvf mlterm-3.8.0.tar.gz
4. cd mlterm 3.8.0
5. ./configure --enable-fribidi
6. make
7. make install
   At this point, mlterm has been added to the $PATH (in /usr/local/bin/)
8. mlterm
   mlterm: error while loading shared libraries: libmlterm_coreotl.so: cannot open shared object file: No such file or directory

However, libmlterm_coreotl.so is present in both ./vtemu/.libs and /usr/local/lib64 (with permissions -rwxr-xr-x, dates differing by 2 seconds, both today, and the same byte length).

What did I do wrong? Or is it impossible to compile mlterm for a 64bit Linux architecture?

The command "file /usr/local/lib64/libmlterm_coreotl.so" answers:
/usr/local/lib64/libmlterm_coreotl.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=6d722b6eb74f520c88b69da3c4f232726845480b, not stripped

Best regards,
Tony.

[Araki Ken]

Hi,

Does LD_LIBRARY_PATH environmental variable contain /usr/local/lib64?
What happens if you execute following commands.

$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib64
$ /usr/local/bin/mlterm

Regards,

[Antoine J. Mechelynck]

$LD_LIBRARY_PATH is not set.

If I execute
LD_LIBRARY_PATH=/usr/local/lib64 mlterm
the mlterm window opens.
However, after that it opens even without the environment setting
(i.e. when started from a konsole tab where $LD_LIBRARY_PATH is still
not set).
/usr/local/bin/mlterm is the only mlterm in the $PATH.

I wonder what was wrong and has been set right. I haven't tried
launching mlterm today before setting that environment variable but I
remember that since I opened this support request there has been a
kernel update (and the reboot that goes with it).

Thanks anyway,
Tony.

On Fri, Mar 31, 2017 at 5:20 PM, Araki Ken arakiken@users.sf.net wrote:

Hi,

Does LD_LIBRARY_PATH environmental variable contain /usr/local/lib64?
What happens if you execute following commands.

$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib64
$ /usr/local/bin/mlterm

Regards,

---

[support-requests:#12] After compiling mlterm on openSUSE Leap 42.2, it
doesn't run

Status: open
Group: v1.0 (example)
Created: Mon Mar 27, 2017 05:47 AM UTC by Antoine J. Mechelynck
Last Updated: Mon Mar 27, 2017 05:47 AM UTC
Owner: nobody

I tried the following in openSUSE Leap 42.2 x86_64:
0. Make sure packages fribidi and fribidi-devel are installed
1. Download the .tar.gz for mlterm 3.8.0
The rest was done in bash running in konsole:
2. tar -zxvf mlterm-3.8.0.tar.gz
3. cd mlterm 3.8.0
4. ./configure --enable-fribidi
5. make
6. make install
At this point, mlterm has been added to the $PATH (in /usr/local/bin/)
7. mlterm
mlterm: error while loading shared libraries: libmlterm_coreotl.so: cannot
open shared object file: No such file or directory

However, libmlterm_coreotl.so is present in both ./vtemu/.libs and
/usr/local/lib64 (with permissions -rwxr-xr-x, dates differing by 2 seconds,
both today, and the same byte length).

What did I do wrong? Or is it impossible to compile mlterm for a 64bit Linux
architecture?

The command "file /usr/local/lib64/libmlterm_coreotl.so" answers:
/usr/local/lib64/libmlterm_coreotl.so: ELF 64-bit LSB shared object, x86-64,
version 1 (SYSV), dynamically linked,
BuildID[sha1]=6d722b6eb74f520c88b69da3c4f232726845480b, not stripped

Best regards,
Tony.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mlterm/support-requests/12/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/