-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A RCP application launch procedure is attempting to load an x86_64 based SWT file while running on a aarch64 system. #1280
Comments
Please try with 4.32 RC2. |
The error persists using the build suggested when launching within the AdoptOpenJDK (11.0.11) environment. It will still launch using AdoptOpenJDK (17.0.8.1). I have included the full terminal output. The relevant error begins at !STACK #1. Terminal error received: !ENTRY org.eclipse.osgi 4 0 2024-06-03 07:10:28.654
|
Launching a product from within Eclipse IDE 2024-03 (RCP-RAP) using an Eclipse Application Configuration returns a failed to load error shown below. This first occurred after updating from Eclipse IDE 2023-09 (RCP RAP). To test the update i removed the .p2 directory and installed a fresh copy of Eclipse IDE 2024-03 (RCP-RAP). I added no additional plug-ins. The error persists.
Building the application (Maven) embedding "org.eclipse.justj.openjdk.hotspot.jre.full.feature.group" version="11.0.23.v20240427-0611" works as expected. All plugins within the RCP application have a compiler compliance level of 11.
WORK AROUND: - set launch configuration execution environment to JavaSE-17.
Looking further I found the following conditions return different results.
Setting the launch configuration execution environment changes the result as follows:
JavaSE-11 (AdoptOpenJDK 11 (11.0.11) produces the error shown below.
JavaSE-17 (AdoptOpenJDK 11 (17.0.8.1) the application launches and executes as expected.
JavaSE-21 (tenuring-21) the application launches but does not function.
Before updating to IDE 2024-03 the configuration execution environment JavaSE-11 was used. The concerning factor is in future IDE's where I might not be able to execute due to the environment.
ERROR:
!SESSION 2024-05-14 14:25:03.597 -----------------------------------------------
eclipse.buildId=unknown
java.version=11.0.11
java.vendor=AdoptOpenJDK
BootLoader constants: OS=macosx, ARCH=aarch64, WS=cocoa, NL=en_US
Framework arguments: -product com.corgroup.bmp.client.product -clearPersistedState
Command-line arguments: -product com.corgroup.bmp.client.product -data /Users/current/dev/projects-e4/client-workspace/../runtime-com.corgroup.bms.single.user.feature.product -dev file:/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/dev.properties -os macosx -ws cocoa -arch aarch64 -consoleLog -clearPersistedState -data @user.home/COR•REC/.cor-rec
!ENTRY org.eclipse.osgi 4 0 2024-05-14 14:25:11.451
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/org.eclipse.osgi/187/0/.cp/libswt-pi-cocoa-4954r7.jnilib: dlopen(/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/org.eclipse.osgi/187/0/.cp/libswt-pi-cocoa-4954r7.jnilib, 0x0001): tried: '/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/org.eclipse.osgi/187/0/.cp/libswt-pi-cocoa-4954r7.jnilib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/org.eclipse.osgi/187/0/.cp/libswt-pi-cocoa-4954r7.jnilib' (no such file), '/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgrou
no swt-pi-cocoa in java.library.path: [/Users/current/Library/Java/Extensions, /Library/Java/Extensions, /Network/Library/Java/Extensions, /System/Library/Java/Extensions, /usr/lib/java, .]
no swt-pi in java.library.path: [/Users/current/Library/Java/Extensions, /Library/Java/Extensions, /Network/Library/Java/Extensions, /System/Library/Java/Extensions, /usr/lib/java, .]
/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib: dlopen(/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib, 0x0001): tried: '/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (no such file), '/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))
Can't load library: /Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa.jnilib
Can't load library: /Users/current/.swt/lib/macosx/x86_64/libswt-pi.jnilib
/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib: dlopen(/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib, 0x0001): tried: '/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (no such file), '/Users/current/.swt/lib/macosx/x86_64/libswt-pi-cocoa-4954r7.jnilib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))
An error has occurred. See the log file
/Users/current/COR•REC/.cor-rec/.metadata/.log.
WORKING:
!SESSION 2024-05-14 14:53:14.382 -----------------------------------------------
eclipse.buildId=unknown
java.version=17.0.8.1
java.vendor=Eclipse Adoptium
BootLoader constants: OS=macosx, ARCH=aarch64, WS=cocoa, NL=en_US
Framework arguments: -product com.corgroup.bmp.client.product -clearPersistedState
Command-line arguments: -product com.corgroup.bmp.client.product -data /Users/current/dev/projects-e4/client-workspace/../runtime-com.corgroup.bms.single.user.feature.product -dev file:/Users/current/dev/projects-e4/client-workspace/.metadata/.plugins/org.eclipse.pde.core/com.corgroup.bms.single.user.feature.product/dev.properties -os macosx -ws cocoa -arch aarch64 -consoleLog -clearPersistedState -data @user.home/COR•REC/.cor-rec
!ENTRY org.eclipse.ui 2 2 2024-05-14 14:53:17.897
!MESSAGE Invalid preference category path: org.eclipse.ui.preferencePages.Workbench (bundle: org.eclipse.equinox.security.ui, page: org.eclipse.equinox.security.ui.category)
The text was updated successfully, but these errors were encountered: