Forum Discussion
OstbergM
Staff
12 years agoHello again,
I did some research into this and came to the conclusion that some parts of JavaFX is compiled using GLIBC_2.11 which is from 2009.
This is about the same year as JavaFX was released, so that pretty much makes sense.
As with many other *nix-libraries you cannot compile with a "new" one and run it with an old one, the other way around usually works though.
To recompile glibc for a specific version can be very dangerous for any distro and is prone to breaking a'lot of stuff.
That is something i would never recommend anyone to attempt doing.
This means that the LoadUI controller will most likely never work in CentOS 5.8 unfortunately.
The agent should work just fine though, as it has been cleaned up from JavaFX dependencies.
An alternative if you are stuck with a production environment that is old and gold is to use virtualization to achieve what you need.
I hope it works out!
Best regards,
Mikael
I did some research into this and came to the conclusion that some parts of JavaFX is compiled using GLIBC_2.11 which is from 2009.
This is about the same year as JavaFX was released, so that pretty much makes sense.
As with many other *nix-libraries you cannot compile with a "new" one and run it with an old one, the other way around usually works though.
To recompile glibc for a specific version can be very dangerous for any distro and is prone to breaking a'lot of stuff.
That is something i would never recommend anyone to attempt doing.
This means that the LoadUI controller will most likely never work in CentOS 5.8 unfortunately.
The agent should work just fine though, as it has been cleaned up from JavaFX dependencies.
An alternative if you are stuck with a production environment that is old and gold is to use virtualization to achieve what you need.
I hope it works out!
Best regards,
Mikael