install xojo 64 bit on CentOS_7

[quote]error: Failed dependencies:
ld-linux-armhf.so.3 is needed by xojo2018r4-2018.04-2.x86_64
ld-linux-armhf.so.3(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libX11.so.6 is needed by xojo2018r4-2018.04-2.x86_64
libatk-1.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libcairo-gobject.so.2 is needed by xojo2018r4-2018.04-2.x86_64
libcairo.so.2 is needed by xojo2018r4-2018.04-2.x86_64
libdl.so.2(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libgcc_s.so.1(GCC_3.0) is needed by xojo2018r4-2018.04-2.x86_64
libgcc_s.so.1(GCC_3.3) is needed by xojo2018r4-2018.04-2.x86_64
libgcc_s.so.1(GCC_4.3.0) is needed by xojo2018r4-2018.04-2.x86_64
libgcc_s.so.1(GLIBC_2.0) is needed by xojo2018r4-2018.04-2.x86_64
libgdk-3.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libgdk_pixbuf-2.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libgio-2.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libglib-2.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libgobject-2.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libgthread-2.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libgtk-3.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libpango-1.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libpangocairo-1.0.so.0 is needed by xojo2018r4-2018.04-2.x86_64
libunwind-arm.so.8 is needed by xojo2018r4-2018.04-2.x86_64
libunwind.so.8 is needed by xojo2018r4-2018.04-2.x86_64
libutil.so.1(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libz.so.1 is needed by xojo2018r4-2018.04-2.x86_64
[/quote]

locate libgcc_s.so.1

in the console and see if it finds a match

/usr/lib64/libgcc_s.so.1

ya I figured because GLIBC installs that so

I don’t know if it is something with the rpm install for Xojo

Have you tried using the TAR download for Xojo?

No
But…
I have an application that works on a CentOS 6 installation 32-bit
But on CentOS 7 64-bit some containers shrink very much and on one Webpage where I put many containers they don’t show up
In debugging mode every show up alright.
Maybe I should try to install 32-bit version
But then off course we have again this problem of installing the 32-bit libraries.

That is why I wanted to install a linux version to debug it directly on the server. It is a web application

I usually build from my Mac then deploy to my Centos 7 x64 web server so yes I’m sure if you are running the IDE on the platform there are many more requirements.

Maybe you are seeing some anomalies due to the fact that it now uses GTK3 instead of GTK2 ?

I compiled 32-bit web with xojo 2018r3 and that works on centOS 32-bit

Did you ever installed 32-bit libraries on a CentOS 7

Should I try:

sudo yum install glib2.i686 libgcc.i686 libstdc++.i686 gtk3.i686 webkitgtk3.i686

or have you another suggestion?

[quote=426302:@roland brouwers]I compiled 32-bit web with xojo 2018r3 and that works on centOS 32-bit

Did you ever installed 32-bit libraries on a CentOS 7

Should I try:

sudo yum install glib2.i686 libgcc.i686 libstdc++.i686 gtk3.i686 webkitgtk3.i686

or have you another suggestion?[/quote]

Yes I have installed x32 libraries on CentOS but that was for running the built web program and not for running the IDE

yes do that, just use yum list xxxxx.i686 to check for available packages first

glib2.i686 2.56.1-2.el7
libgcc.i686 4.8.5-36.el7
libstdc++.i686 4.8.5-36.el7
gtk3.i686 3.22.30-3.el7
webkitgtk3.i686 2.4.11-2.el7

This is the result

I did install the 32-bit libraries
but the app doesn’t start
but now

[quote]error: Failed dependencies:
ld-linux-armhf.so.3 is needed by xojo2018r4-2018.04-2.x86_64
ld-linux-armhf.so.3(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libdl.so.2(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libunwind-arm.so.8 is needed by xojo2018r4-2018.04-2.x86_64
libunwind.so.8 is needed by xojo2018r4-2018.04-2.x86_64
libutil.so.1(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
[/quote]

A lot shorter

It is midnight in Belgium. Maybe if you could have a look at it and tell me tomorrow. Only 6 pieces left.
I thank you very much for all the effort and assistance.

Ok will do and you are very welcome

What is left:

[quote]error: Failed dependencies:
ld-linux-armhf.so.3 is needed by xojo2018r4-2018.04-2.x86_64
ld-linux-armhf.so.3(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libdl.so.2(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
libunwind-arm.so.8 is needed by xojo2018r4-2018.04-2.x86_64
libutil.so.1(GLIBC_2.4) is needed by xojo2018r4-2018.04-2.x86_64
[/quote]
libdl.so.2 is provided by ‘Package glibc-2.17-260.el7_6.3.i686 already installed and latest version’
libutil.so.1 is provided by ‘Package glibc-2.17-260.el7_6.3.i686 already installed and latest version’
The others are a puzzle
any idea?

Sorry I’m so late to this party, but you don’t need to do all of that stuff. The dependencies in the RPM are simply wrong. The only way to install is via the tgz file.

Download it to your Downloads folder and do this in a Terminal:

sudo -s yum -y install gtk3 gtk3-devel libunwind cd /opt mkdir xojo cd xojo tar -zxvf ~/Downloads/xojo2018r4.tgz

Next, add this file to /usr/share/applications/:
https://www.dropbox.com/s/ymcl05hvfq5mvxt/xojo2018r4.desktop?dl=1

You still need to use sudo to add any plugins to the resulting install in /opt/xojo/xojo2018/Plugins.

You’re now there based on my experience with CentOS 7.5.

One more note - when you look into the Start menu, you will need to execute Xojo from the “Recently Installed” option before it shows up properly under “Development”.

I’ll create a note that Jason can pin for Fedora/CentOS/SuSE since this applies to all three.

I would like to do this a clean way.
I have a snapshot of this CentOS 7 installation. I can do a rollback
What should I install first
Gnome Kde httpd …

I can download the tar file. But how does this work together with the link of the desktop file?

If you’re starting clean, simply follow the steps above and you’re good to go. That’s what those steps apply to.

As I understand you have experience with CentOS 7.
I would like to install Xojo on CentOS 7, because my application doesn’t work properly anymore.
I embed containers on a webpage in the open event.
One container shrinks considerably and a group of containers disappear.
Did you have any experience of a kind?