Re: jEdit on Mac mini w/M1 & Big Sur

Matthieu Casanova <[email protected]>
Newsgroups gmane.editors.jedit.user
Message-ID <[email protected]>
Hey Thomas,
I just bought a Mac M1 and ran into the same problem, when I double click on the icon it says that I need java 11.
But when running from the console

java - jar jEdit.jar
jEdit runs without any problem. I’m not a Mac expert and am not sure how to tell the OS which java it should use

Matthieu

> Le 22 mai 2021 à 20:08, Thomas Meyer <[email protected]> a écrit :
> 
> Hi,
> 
> Can you please try to start jEdit in the Terminal:
> 
> $ /path/to/java -jar /path/to/jedit.jar
> Does this work for you?
> 
> Path to Java is probably /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/bin/java
> 
> Path to jedit.jar is probably /Applications/jEdit/something/jedit.jar
> 
> Mfg
> Thomas 
> 
> Am 22. Mai 2021 14:42:06 MESZ schrieb David Filip <[email protected] <mailto:[email protected]>>:
> Sent a message about 10 days ago, but got a message back saying it was too big.  As I have not yet found a solution, I am editing then down, and hope that this makes it through, and that someone out there can provide any advice.
> 
> Begin forwarded message:
> 
> From: David Filip <[email protected] <mailto:[email protected]>>
> Subject: jEdit on Mac mini w/M1 & Big Sur
> Date: May 13, 2021 at 9:11:57 AM EDT
> To: [email protected] <mailto:[email protected]>
> 
> Hi All!
> 
> I’m trying to run the latest jEdit on a shiny new Mac Mini with the M1 chip (Apple silicon) and Big Sur.
> 
> I am getting the error: [image removed]
> 
> This application required that Java 11 or later be installed on your computer.  Please download and install the latest version of Java from www.java.com <http://www.java.com/> and try again.
> 
> I have defined JAVA_HOME in my .bash_profile:
> 
> 	export JAVA_HOME=/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
> 
> which appears to be correct:
> 
> 	$ which java
> 	/usr/bin/java
> 
> 	$ java -version
> 	openjdk version "11.0.11" 2021-04-20 LTS
> 	OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
> 	OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)
> 
> 	$ echo $JAVA_HOME
> 	/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home
> 
> 	$JAVA_HOME/bin/java -version
> 	openjdk version "11.0.11" 2021-04-20 LTS
> 	OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
> 	OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)
> 
> although as you can see, I have installed the Azul / Zulu port, as it is the only ARM64 (M1) port of the JVM that I could find.  It is one of the new “Universal Binary” files that contains both Intel and ARM executables:
> 
> 	$ file `which java`
> 	/usr/bin/java: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64 [arm64e:Mach-O 64-bit executable arm64e]
> 	/usr/bin/java (for architecture x86_64):	Mach-O 64-bit executable x86_64
> 	/usr/bin/java (for architecture arm64e):	Mach-O 64-bit executable arm64e
> 
> As I understand it, Oracle specifically does not support ARM64 (M1), and also has potential licensing issues (since about a year ago).
> 
> Therefore, I am not sure if the problem is that jEdit is finding the JRE but doesn’t recognize the Zulu build, or that it is not finding it at all, and I somehow need to tell jEdit where to find it?
> 
> Has anyone gotten jEdit working on a ARM64 / M1 Mac running Big Sur, and if so how?
> 
> Please advise.
> 
> Thanks,
> 
> Dave.
> 
> 
> -- 
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.-- 
> -----------------------------------------------
> jEdit Users' List
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/jedit-users <https://lists.sourceforge.net/lists/listinfo/jedit-users>

-- 
-----------------------------------------------
jEdit Users' List
[email protected]
https://lists.sourceforge.net/lists/listinfo/jedit-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.