[Linux] SDK fails to start on RHEL 7.9 since I20241127-1240, requires GLIBC_2.34

[iloveeclipse]

Either I've missed the announcement or we have an issue with supporting older Linux installations with 4.35.
I'm unable to start latest IBuild on RHEL 7.9, same build works fine on RHEL 9.2.

IDE shows splash screen and after that an error dialog.

Log shows that we have an implicit requirement of GLIBC_2.34 now.
I have GLIBC_2.17 (glibc-2.17-317.el7.i686) on RHEL 7.9:

rpm -qa | sort | grep glibc
glibc-2.17-317.el7.i686
glibc-2.17-317.el7.x86_64
glibc-common-2.17-317.el7.x86_64
glibc-debuginfo-2.17-317.el7.x86_64
glibc-debuginfo-common-2.17-317.el7.x86_64
glibc-devel-2.17-317.el7.i686
glibc-devel-2.17-317.el7.x86_64
glibc-headers-2.17-317.el7.x86_64

!SESSION 2024-12-02 13:50:14.865 -----------------------------------------------
eclipse.buildId=4.35.0.I20241201-1800
java.version=21.0.2-13
java.vendor=N/A
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.osgi 4 0 2024-12-02 13:50:30.814
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
	/home/aloskuto/Downloads/eclipse435/eclipse/configuration/org.eclipse.osgi/267/0/.cp/libswt-pi3-gtk-4968r2.so: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /home/aloskuto/Downloads/eclipse435/eclipse/configuration/org.eclipse.osgi/267/0/.cp/libswt-pi3-gtk-4968r2.so)
	no swt-pi3-gtk in java.library.path: /opt/rh/devtoolset-11/root/usr/lib64:/opt/rh/devtoolset-11/root/usr/lib:/opt/rh/devtoolset-11/root/usr/lib64/dyninst:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/vobs/zenith/workspace/lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/fw/hpl/sh_lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/segments/eclipse/eclipseRE/sh_lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/sdk/lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/ure/lib:/opt/hp93000rt/el7/x86_64/ace-tao_6.2.4/ACE/lib64:/opt/hp93000rt/el7/x86_64/ruby-1.8.6/lib:/opt/hp93000rt/el7/x86_64/log4cxx_0.11.0_snapshot/lib:/opt/hp93000rt/el7/x86_64/imkl_3:/opt/hp93000rt/el7/x86_64/libstdf_0.4/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
	no swt-pi3 in java.library.path: /opt/rh/devtoolset-11/root/usr/lib64:/opt/rh/devtoolset-11/root/usr/lib:/opt/rh/devtoolset-11/root/usr/lib64/dyninst:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/vobs/zenith/workspace/lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/fw/hpl/sh_lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/segments/eclipse/eclipseRE/sh_lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/sdk/lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/ure/lib:/opt/hp93000rt/el7/x86_64/ace-tao_6.2.4/ACE/lib64:/opt/hp93000rt/el7/x86_64/ruby-1.8.6/lib:/opt/hp93000rt/el7/x86_64/log4cxx_0.11.0_snapshot/lib:/opt/hp93000rt/el7/x86_64/imkl_3:/opt/hp93000rt/el7/x86_64/libstdf_0.4/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi3-gtk-4968r2.so
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi3-gtk.so
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi3.so
	/home/aloskuto/.swt/lib/linux/x86_64/libswt-pi3-gtk-4968r2.so: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi3-gtk-4968r2.so)

	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345)
	at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254)
	at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:99)
	at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:209)
	at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:155)
	at org.eclipse.swt.widgets.Display.<clinit>(Display.java:170)
	at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:754)
	at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:185)
	at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:208)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:143)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:109)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:439)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:271)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:668)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:605)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1481)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1454)
	Suppressed: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 
	/home/aloskuto/Downloads/eclipse435/eclipse/configuration/org.eclipse.osgi/267/0/.cp/libswt-pi4-gtk-4968r2.so: libgtk-4.so.1: cannot open shared object file: No such file or directory
	no swt-pi4-gtk in java.library.path: /opt/rh/devtoolset-11/root/usr/lib64:/opt/rh/devtoolset-11/root/usr/lib:/opt/rh/devtoolset-11/root/usr/lib64/dyninst:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/vobs/zenith/workspace/lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/fw/hpl/sh_lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/segments/eclipse/eclipseRE/sh_lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/sdk/lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/ure/lib:/opt/hp93000rt/el7/x86_64/ace-tao_6.2.4/ACE/lib64:/opt/hp93000rt/el7/x86_64/ruby-1.8.6/lib:/opt/hp93000rt/el7/x86_64/log4cxx_0.11.0_snapshot/lib:/opt/hp93000rt/el7/x86_64/imkl_3:/opt/hp93000rt/el7/x86_64/libstdf_0.4/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
	no swt-pi4 in java.library.path: /opt/rh/devtoolset-11/root/usr/lib64:/opt/rh/devtoolset-11/root/usr/lib:/opt/rh/devtoolset-11/root/usr/lib64/dyninst:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/vobs/zenith/workspace/lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/fw/hpl/sh_lib:/workspaces/socbm262/aloskuto/ws-r7.10-aloskuto-bf/opt/93000/src/segments/eclipse/eclipseRE/sh_lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/sdk/lib:/opt/hp93000rt/el7/x86_64/ure_udk_74/ure/lib:/opt/hp93000rt/el7/x86_64/ace-tao_6.2.4/ACE/lib64:/opt/hp93000rt/el7/x86_64/ruby-1.8.6/lib:/opt/hp93000rt/el7/x86_64/log4cxx_0.11.0_snapshot/lib:/opt/hp93000rt/el7/x86_64/imkl_3:/opt/hp93000rt/el7/x86_64/libstdf_0.4/lib:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi4-gtk-4968r2.so
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi4-gtk.so
	Can't load library: /home/aloskuto/.swt/lib/linux/x86_64/libswt-pi4.so
	/home/aloskuto/.swt/lib/linux/x86_64/libswt-pi4-gtk-4968r2.so: libgtk-4.so.1: cannot open shared object file: No such file or directory

		at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345)
		at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254)
		at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:103)
		... 18 more

I assume this is regression from either ca1bb19 or c984d14

[iloveeclipse]

@akurtakov, @laeubi : at Advantest we are forced to provide support for older Linux versions because our product runs (once adopted by customers) typically for many years in unchanged production environment. So we are supporting RHEL 7.9 till end of 2025 at least, even if we also support same product version running on RHEL 9.2.

Dropping RHEL 7.9 support would be not nice, at least till 2026.

I assume that the glibc requirement is coming from compilation on latest ubuntu (#1624), as I don't see explicit requirement on GLIBC 2.34 in the SWT sources.

Isn't there a way to compile GTK3 related SWT code in a way it doesn't require GLIBC 2.34?

[akurtakov]

Compilation actually happens on debian 12 for #1422 . Waiting for 2026 to start providing gtk 4 builds looks like the final nail for swt so I don't have a clue how I can help you.

[laeubi]

Either I've missed the announcement or we have an issue with supporting older Linux installations with 4.35.

The announcement is here: https://www.eclipse.org/lists/platform-dev/msg04085.html

Advantest we are forced to provide support for older Linux versions because our product runs (once adopted by customers) typically for many years in unchanged production environment. So we are supporting RHEL 7.9 till end of 2025 at least, even if we also support same product version running on RHEL 9.2.

Then the best opportunity is to either use the backports (I think IBM offers support for such older builds @MohananRahul might can tell more) or build an own version of SWT.

As RHEL 7.9 is EOS since June this year this seems like something customers should be aware of that products might not support this anymore.

Isn't there a way to compile GTK3 related SWT code in a way it doesn't require GLIBC 2.34?

Basically that would be possible but:

1. requires additional complications of the build scripts (or some investigation of how to use older libc versions in parallel)
2. might require people that like to maintain that
3. ... maybe more ...

So depending on how important that topic is to Advantest, the best would be to reach out to IDE WG and organize with their efforts, I probably can try to support in that area but I'm not the driving force behind this initiative.

Beside that, until 2026 it might even happen that GTK3 is completely dropped if no one steps up in its further maintenance.

[iloveeclipse]

@laeubi : thanks. I see your message says:

As part of this effort it was required to update some build dependencies resulting in a higher version of GLIBC (at least 2.36 for x86 other architectures might require higher versions) this usually means you need at least:

• Debian 12 or recent Ubuntu
• Centos 9

On RHEL 9.2 (from which CentOS 9 is built) we have GLIBC 2.34 which is below of GLIBC 2.36 what you've mentioned.

Is this expected that RHEL 9.2 is also not supported and works "by chance" now?

[laeubi]

On RHEL 9.2 (from which CentOS 9 is built) we have GLIBC 2.34 which is below of GLIBC 2.36 what you've mentioned.
Is this expected that RHEL 9.2 is also not supported and works "by chance" now?

The main problem is that CentOS 9 is no longer a "stable" release but a roiling one (from what I have understood), the closes we could found compared to what we previously had with centos was Debian LTS releases and that's what we compile against, and running against latest ubuntu, so there is absolutely possible that RHEL/Centos only "work by chance" unless there is some efforts to even run the tests on different distributions.

At least you have verified now it runs on RHEL 9.2 and @akurtakov uses Fedora, not sure if we have more variations (I test under Debian 12 directly).

[iloveeclipse]

CentOS 9 is no longer a "stable" release but a roiling one (from what I have understood)

This is new, not sure your are on the right track. We have chosen RHEL because of the enterprise support and platform stability guaranteed. Rolling release is per definition not stable so from my experience since (RHEL 5) I doubt RHEL 9 is "rolling" release.

But once again: is GLIBC 2.36 the minimum required version now? If yes, RHEL 9.2 is not supported then?

[laeubi]

This is new, not sure your are on the right track. We have chosen RHEL because of the enterprise support and platform stability guaranteed. Rolling release is per definition not stable so from my experience since (RHEL 5) I doubt RHEL 9 is "rolling" release.

RHEL 9 != Centos 9 but I'm not that deep in that topic and its mostley marketing / business decision I'm not involved in.

Also Eclipse Infra only supports ubuntu now see here:

https://github.com/eclipse-cbi/jiro-agents/tree/master?tab=readme-ov-file#jiro-agents

so when we want RHEL 9 we probably need dedicated machine/licence/whatever/ ...

But once again: is GLIBC 2.36 the minimum required version now? If yes, RHEL 9.2 is not supported then?

according to the error you send here and with this command (thanks to @akurtakov for the hint) :

/git/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.linux.x86_64$ nm -D *.so |grep GLIBC|sort -u
                 U dlopen@GLIBC_2.34
                 U dlsym@GLIBC_2.34
                 U fflush@GLIBC_2.2.5
                 U fprintf@GLIBC_2.2.5
                 U free@GLIBC_2.2.5
                 U getenv@GLIBC_2.2.5
                 U localeconv@GLIBC_2.2.5
                 U malloc@GLIBC_2.2.5
                 U memcpy@GLIBC_2.14
                 U memmove@GLIBC_2.2.5
                 U memset@GLIBC_2.2.5
                 U realpath@GLIBC_2.3
                 U setenv@GLIBC_2.2.5
                 U stderr@GLIBC_2.2.5
                 U strcmp@GLIBC_2.2.5
                 U strlen@GLIBC_2.2.5
                 U strtok@GLIBC_2.2.5
                 w __cxa_finalize@GLIBC_2.2.5

actually 2.34 is the minimum (as of today!)

[akurtakov]

@iloveeclipse Times have changed ( https://blog.centos.org/2020/12/future-is-centos-stream/ ) and RHEL is no longer upstream for CentOS but rather the opposite.

[iloveeclipse]

For RHEL 7 we will evaluate a (local) rebuild of SWT natives on RHEL 7.

For the record, RH customer portal lists following versions of glibc for RHEL 9.4 (latest released):

The only available choice is GLIBC 2.34.

So it would be nice we could at least keep that level in SWT.

[trancexpress]

Hi @laeubi ,

what options do we have to rebuild SWT Linux GTK3 64 bit natives during our platform builds? We want to build those locally, assuming that this fixes our problem (for now at least).

I tried bumping versions of SWT binary bundles (and SWT itself), but the use of the versions doesn't seem to be limited to just SWT. I'm guessing something is generating expected versions (that no longer match what I've bumped); I find nothing in the git repository at least, that uses the strict version mentioned in the mvn errors:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10:02 min
[INFO] Finished at: 2024-12-09T14:34:26+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Cannot resolve dependencies of project org.eclipse.rcp.feature:org.eclipse.rcp:eclipse-feature:4.35.0-SNAPSHOT
[ERROR]  with context {osgi.os=linux, osgi.ws=gtk, org.eclipse.update.install.features=true, org.eclipse.jdt.buildtime=true, osgi.arch=x86_64, org.eclipse.update.install.sources=true}
[ERROR]   Software being installed: org.eclipse.rcp.feature.group 4.35.0.qualifier
[ERROR]   Missing requirement: org.eclipse.e4.rcp.feature.group 4.35.0.v20241206-2256 requires 'org.eclipse.equinox.p2.iu; org.eclipse.swt [3.129.0.v20241206-0950,3.129.0.v20241206-0950]' but it could not be found
[ERROR]   Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.35.0.qualifier depends on: org.eclipse.equinox.p2.iu; org.eclipse.e4.rcp.feature.group 0.0.0: See log for details
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot resolve dependencies of project org.eclipse.rcp.feature:org.eclipse.rcp:eclipse-feature:4.35.0-SNAPSHOT
 with context {osgi.os=linux, osgi.ws=gtk, org.eclipse.update.install.features=true, org.eclipse.jdt.buildtime=true, osgi.arch=x86_64, org.eclipse.update.install.sources=true}
  Software being installed: org.eclipse.rcp.feature.group 4.35.0.qualifier
  Missing requirement: org.eclipse.e4.rcp.feature.group 4.35.0.v20241206-2256 requires 'org.eclipse.equinox.p2.iu; org.eclipse.swt [3.129.0.v20241206-0950,3.129.0.v20241206-0950]' but it could not be found
  Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.35.0.qualifier depends on: org.eclipse.equinox.p2.iu; org.eclipse.e4.rcp.feature.group 0.0.0

Best regards and thanks,
Simeon