Hello,
I've got an Ubuntu20 PC where I develop all my MUMPS routines and compiling it (UTF8 is set and LIBICU 66).
Then, when I deploy those scripts on a brand new Ubuntu22 server, the compilation works fine (generating .o files with mumps .m). On this serveur, I only have LIBICU 70.
But when I try to use our application, I've got error
How can I check that those m files are compiled the right way , because installing LIBICU66 seems to almost solve the problem ?
Is this normal after having compiled on the local server ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you provide the exact error you get when you try to use the application.
There is no compatibility issue between icu70 and icu66. The fact that installing icu66 solves the problem indicates that your environment has hard coded icu66 in its expectation. If you are able to find where gtm_icu_version is set and if you see that it has 6.6, changing that to 7.0 should solve the issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I've got an Ubuntu20 PC where I develop all my MUMPS routines and compiling it (UTF8 is set and LIBICU 66).
Then, when I deploy those scripts on a brand new Ubuntu22 server, the compilation works fine (generating .o files with mumps .m). On this serveur, I only have LIBICU 70.
But when I try to use our application, I've got error
How can I check that those m files are compiled the right way , because installing LIBICU66 seems to almost solve the problem ?
Is this normal after having compiled on the local server ?
Can you provide the exact error you get when you try to use the application.
There is no compatibility issue between icu70 and icu66. The fact that installing icu66 solves the problem indicates that your environment has hard coded icu66 in its expectation. If you are able to find where gtm_icu_version is set and if you see that it has 6.6, changing that to 7.0 should solve the issue.