oh the jar launcher? wlep, i was using the app itself instead, now i just tried tha .jar file but it says that it cannot be launched for some reason, in case i'm pulling this hit right here:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Java 17 for 10.8, 10.9, 10.10, and 10.11 & Java 11 for 10.6-10.11 (JDK)
- Thread starter Jazzzny
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
damn it didn't post my reply. so i was using the app but then as you mentioned the jar file i still run into troubles. it says that it cannot open it so i opened the console and i got this. idk if i'm doing it wrong i just double click the jar file because i have no idea how to run the jar file in other ways.
EDIT: it did post my reply sorry abt that, for some reason it wasn't showing my previous reply lol
for some reason it's not posting my replies, i tried to check the java version and it shows up like this, not sure what does it means, but still tried launching the .jar atlauncher but no luck, the log says the same thing in the terminal, i'll try to search any possible fix
Attachments
I'm also having this same issue on SL, if I somehow work it out (and remember to post it) I will post it here
edit: got it working, not sure exactly how, but I reran the installer (I forgot that there is that command at the end of the installer that needed to work, I was googling how to set a java as the default, which was wrong or something) I did also reboot after the install as well but that's all I have, ATLauncher though is being annoying though as it insists that it isn't alone in its folder despite me putting it in its own folder, meaning all data (login, instances, settings, etc) get erased every time I launch it (also I had to do it from the terminal too)
Last edited:
hi, sorry but do u have an archive of the jdk-11-snowleopard-r1.pkg , its not archvied anywhere and i want to run 1.16.5 on snow leopard
MultiMC works, tested (OS X 10.9.5) on a MacBookPro11,3 with 16 GB RAM.
Tends to get anywhere from 80 to 100 without OptiFine (on default settings, except VSync is off)
with OptiFine it gets around 200 fps consistantly (on default settings, except VSync is off)
Tends to get anywhere from 80 to 100 without OptiFine (on default settings, except VSync is off)
with OptiFine it gets around 200 fps consistantly (on default settings, except VSync is off)
Attachments
Last edited:
wait can you add the Java 21 to the old build system too as that is the only one we can currently download from?
thank you so much, im gonna use SKLauncher probably cuz multimc too new for SL (sklauncher needs java 8 min so runs on any os with java 8+)
EDIT: SKLauncher didnt work cuz it needs javaFX, so i used Legacy Laucher and that worked fine (Options -> Use System JRE)
Last edited:
How did you manage to log in? Did you use another computer, and transfer it over?MultiMC works, tested (OS X 10.9.5) on a MacBookPro11,3 with 16 GB RAM.
Tends to get anywhere from 80 to 100 without OptiFine (on default settings, except VSync is off)
with OptiFine it gets around 200 fps consistantly (on default settings, except VSync is off)
Yes, I did. I had to transfer the accounts.json file from a Windows Vista laptop, which was already logged in to MultiMC. If you transfer correctly, it should work. I *did* have some trouble using the same accounts.json on a Mac Mini running OS X 10.8 (launch OS) so OS X 10.8 and before *may* not be able to connect to Microsoft servers correctly.
Thanks for you efforts Jazzzny. I'm currently trying to build JDK17u for El Capitan (10.11) using your patches. Can you please elaborate where (host OS) and how (configure) you're building it exactly? I tried to build it on 10.11 itself but that doesn't work, which is probably why you required 10.12 in your old build instructions. I managed to get things built on Ventura by setting SDKROOT to the MacOSX10.11.sdk and configuring with --with-extra-cxxflags="-stdlib=libc++". The original build instructions (by OpenJDK) didn't work for me because of the stdlib issues. However, java then immediately segfaults on 10.11 in the same way as the official/upstream 17u build (temurin).
Any idea?
Hello,
The instructions are currently a bit incomplete as I've had problem finding time to get things wrapped up neatly.
The JDK needs to be statically linked with libMacportsLegacySupport.a for a few functions such as clock_gettime, or the compiled binaries need to have libSystem.B.dylib replaced with libMacportsLegacySystem.B.dylib using install_name_tool -change.
You can obtain these prebuilt from MacPorts or compile them from the source at https://github.com/macports/macports-legacy-support.
Thanks, I'll look into that. I'd still like to know what host OS version you use to build on and, if so, if you use the target's macOS SDK in any way.
Cheers
Cheers
Nice! That did indeed help to run a clean build without resorting to SDK changes or stdlib overrides. However, it still runs into a segfault while in libjli (java_md_macosx.m), so early during JVM launch. I tested the same (server) build on a different machine on 10.9, and I even tried a minimal JVM build. Same error. I'm out of clues now 😒
I'll try building from the newest source and seeing if anything changed, though it may be related to the compiler used. When I tried setting up GitHub Actions, the builds just wouldn't work for some reason
Thanks! I used JDK17u 17.0.13-ga as baseline, applied your patches/script and built on Ventura (x86_64), using clang 15 (default) against (static) legacy support 1.3.0.