Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] Eclipse Platform Build
  • From: Vishnu Sarath <vishnu.sarath@xxxxxxxxxxx>
  • Date: Thu, 1 Jun 2023 06:09:11 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=xOeJeNELVBeFnPGpbU0v/JFzPTNjmIXQiT16NZzhLYc=; b=XS2grZz97qZdNWGk25EVOyxNrOlcMNv5G4bC9x1ABRQPEYf3P9YBPsrM0bAEQHdgsMgHCusgPaRtWkqzefYjzucR3OPbZO91xdr8RV5w6/AU0lgYsnQkVvzvbm4BlpWcHXfG2WX2pf5TEh702WKXhz5AzjQjA5COnpTKB5cmW+9k2kuySFJZ0ON9ivRFlVGEd0PQsppmBvgm7jHl1J7XEMblSuT9RWcvJ+GZ+PP34IRx56IpjjzvkZz5SU1g1F7G1KXobTedTIUeXTl45/KWkL73BH7sv7c9hTg5LsWsn62fC7NsrXaVoOrTmMDtTH9PvDrzdyVRPmg8G9vyfeKtcQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=FawDX/2KO/G4buhdXePQd/sXA++n+cDwkDK1JFDW7u15lkeFcNIgGPGdBp3LqmP5usT7yWgVPBxAbsUt3t8fJ7eFkMFwkTp8S5k+YN4s9HLgEv0qtpoc4gvJH9UM2F2Of0sywBDCDCMTOmoy+DoviMRFb/O9r88Y4k7PkJTtPKBJlrCCms8+KrK6Pey/yfTrNkgU3xC5ncQxOkVp3FV13GXWxAIQG+zhmnTwN14yXybSyt3E5QMAsG3p7cEtS+PmSFHA5eW+sP4VFVT/bDEMDUFaDKI//k6eXEEimM3aa/NdvLmX0KO8/BdvfsOqDHz1OC1bCRlKwMt0SYtRDKxHBw==
  • Delivered-to: platform-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AdmNdefGHdWlhfZgRa6AdbAaAQaQiAACGEmgACV4XxAAAL7LgAAtu4UAAV/If9A=
  • Thread-topic: [platform-dev] Eclipse Platform Build

Thanks @mistria@xxxxxxxxxx for the detailed mail. I was trying out the things mentioned.


Please see the below steps I tried:


  • Setup a Fedora38 VM.
  • We suspect this commit (which was done to make 3.22 GTK version as minimum), as the cause of the crash issue we are seeing (not sure, need to confirm). The crash occurs when we are right clicking (when trying to show a pop up menu) - getting gtk_menu_popup_at_pointer undefined symbol. Since this may not be present in gtk4. Earlier we used to have a separate handling if the gtk version was less than 3.22. I tried to add the removed native call and changes in And created the .so files with building in Fedora38 VM (Glibc 2.37).
  • But when I am using this .so files in the product and trying to launch the product in SUSE12 SP5, the launch itself is failing. When I tried find the root cause (adding some logs) I got the below error:

/home/vishnu/Downloads/RiscFreeSetupv23.2.1/RiscFreeProduct-INTEL-linux.gtk.x86_64/configuration/org.eclipse.osgi/277/0/.cp/ /lib64/ version `GLIBC_2.34' not found (required by /home/vishnu/Downloads/RiscFreeSetupv23.2.1/RiscFreeProduct-INTEL-linux.gtk.x86_64/configuration/org.eclipse.osgi/277/0/.cp/

               It’s expecting Glibc version above 2.34 while the SUSE12 is having 2.22 by default.


I am a bit new to this, so could someone please guide me on how to fix this. Is this issue because I am using a wrong platform (with higher version of Glibc 2.37 for building). What is the ideal platform which we are using to generate swt .so files for linux gtk.





From: Mickael Istria <mistria@xxxxxxxxxx>
Sent: Wednesday, May 24, 2023 1:40 PM
To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
Cc: Vinod Appu <vinod.appu@xxxxxxxxxxx>
Subject: Re: [platform-dev] Eclipse Platform Build




Please see for explanation of how to build the Eclipse Platform and for particular GTK stuff.

The version of SWT was bumped by +0.1.0 during last cycle, which means it has new APIs and some bundles are probably consuming those new API; so by auditing the version, it seems like the combination you wish to achieve (latest platform with old SWT) is then not possible.

With the link above and good knowledge of Maven, Tycho and PDE, you may be able to hack something to enforce another locally built version of SWT, but overall it will be annoying and difficult for questionable value. If you can make a PR that fixes while still working with supported environments, there are chances that it get merged and than part of the official build. This is IMO the most profitable path forward, although it's not certain it can work.

Note that if you're stuck in an environment that is not supported anymore, you may consider alternative distributions of Eclipse IDE, such as Flatpak one; with such container-like installations, most libs -including GTK- are supposed to be included in a compatible way. .



Back to the top