Page 1 of 1

A mysterious problem with QT5 (Bionic 32)

Posted: Fri Sep 23, 2022 11:20 pm
by dorothee

Hello everybody,

I am facing a very mysterious problem which appeared suddenly : with Bionic 32, I am (was) using an app named Eulexis which was compiled with QT5. When I installed it some libraries were missing but I resolved it promptly. But suddenly the app does not work any more and gives me the message :

Eulexis: undefined symbol: ucnv_getDefaultName_51

I understood that it is a problem with QT, but why did this happen now and not before? I had made some new savefiles, but with no differences about Eulexis.

Very mysterious to me...
If someone has an idea to help me, you can find the app HERE http://depositfiles.com/files/xlc7nasvc and the missing libraries THERE http://depositfiles.com/files/3b8esewdx (about libraries, I am not sure anymore of nothing)

Merci d'avance !


Re: A mysterious problem with QT5 (Bionic 32)

Posted: Sat Sep 24, 2022 7:56 am
by williams2

An undefined symbol usually means that a shared object library file that an executable or another library file is trying to use, is not compatible.

The symbol is the name of a function in an so library file but that function does not seem to exist.
It is a QT5 library file.
The value of the symbol is the name of the codepage for the file that is being edited.
If the function can't figure out the codepage from the data in the file,
it returns "us ascii" as the default codepage.

The executables and the library files of the application and of the operating system, all need to be compatible with each other. Opening a text terminal in the directory that contains the Eulexis executable and typing ldd -v like this:

ldd -v Eulexis

(whatever the name of the executable is)
should show information about what dependencies are needed.

If it was working and now does not work,
one of the applications file may have changed, maybe from an automatic update,
or a QT5 file may have changed, maybe an update, or maybe installing an application changed a library file,
or maybe the LD_LIBRARY_PATH got changed,
or maybe a configuration file got changed,
or something else.

If you start Puppy without a save file (pfix=ram)
and install the application and dependencies,
then obviously something got changed in the save file/folder.
Any changes to the file system should be in the save file.folder.