pyinstaller / pyinstaller/pyinstaller

libreadline.so.6 error on Suse12

Open
#4,657 45 comments 0 reactions 1 assignee View on GitHub

@htgoebel is already working on this.

Since Feb 8, 2020.

@medium bug platform:Linux
Dominant language
Python
Stars
13.1k
Forks
2k
Avg merge
1d 3h
Merged PRs (30d)
11

Description

I'm using PyInstaller to pack my application for distribution on Linux servers.
To support a large amount of Linux flavors and versions I'm using Docker image with an old glibc version to build and pack the application.

Everything working on Ubuntu/Debian/Rhel/CentOS & Suse11, when I tried to run the application on Suse12 server and got this error:

/bin/sh: /dist/app/libreadline.so.6: no version information available (required by /bin/sh)
/bin/sh: relocation error: /bin/sh: symbol rl_filename_stat_hook, version READLINE_6.3 not defined in file libreadline.so.6 with link time reference

What is this library for?

The libreadline version in the building machine is 6.1-1

(test) root@aed98870a11d:/# dpkg -l | grep libreadline
ii  libreadline-dev                 6.1-1                          GNU readline and history libraries, developm
ii  libreadline6                    6.1-1                          GNU readline and history libraries, run-time
ii  libreadline6-dev                6.1-1                          GNU readline and history libraries, developm

It looks like some of the code is running (I can see some output) but not sure if all aspects are working.
I'm still investigating this and will update if I get any new information.

Update:
Building a simple "Hello World" executable works without this error so it is probably one of my import that causes this issue.

If I will upgrade readline version before building python will it help?

PyInstaller: 3.6
OS: Linux (Suse12)
Python: 3.7.5/2.7.16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.