MacOS sucks... and the hardware isn't much better.

What kind of laptop doesn't have an ethernet port? Or USB A of any kind? A dongle/dock is damn near a requirement! And in this day and age, why the hell is there no kind of right-click, until you dig through the settings and activate it?

Having fun (not) testing out getting switch things to build with this thing. I couldn't quickly find a mac equivalent to "python3 is python", so I had to learn that 1) The default terminal uses zsh in the latest macos, and even after you learn how to show hidden files, there actually isn't a .zshrc in existence. You have to "touch .zshrc" to create it, then open it, to enter the required "alias python='python3'" (and I think also for pip3? My head hurts...)

But did that take care of EVERYTHING? HELL NO, it didn't. Because for some reason, while building Atmosphere, the build process somehow ends up calling @python in bash, and bash can't find the command "ptython". So I do the same process creating .bashrc. Didn't work. Tried again with .bash_profile. Didn't work. Found out that contrary to what a Google search showed me, python3 is installed in /usr/bin, and not /usr/local/bin (where I found dkp-pacman living happily). And the system will not let you add/touch anything in usr/bin. So... I made an alias (shortcut) of python3 that saved to my desktop, renamed it to python, then moved it to /usr/local/bin, where is asked for my fingerprint or password, but at least let me do it.

Now that I've finally completed the build (changed like 3 .mk files, to say @python3, to complete the build), I'm now cloning fresh, and trying again to see if the alias works.


Aaaaand... it does not. Permission denied. Why? Dunno. But changed my shell to bash, hard quit the terminal and reopened it, then typed "python"... and it ran. Tried to "make" again, and again I hit the error
Code:
bash: python: command not found

WTF? Too late now. Going to shower and sleep. :hateit:
  • Like
Reactions: SylverReZ and IC_

Comments

I...actually like macOS as a general-use OS. I find it much easier to use, and far more intuitive, than Windows, that's for sure.

Oh, I can easily admit the hardware is overpriced and doesn't offer many port options at all, and it's not exactly compatible with a lot of programs or the like, but the OS itself is still quite good IMHO.
 
i guess it depends on your mac if you have ethernet ;) I have 4...all "ancients" from 2011-2014. upgraded SSD's and OCLP to make newer macos work on them. I even have Sonoma working on a 2011 iMac :D I even bought the magic trackpad because I liked it on the macbook so much! that's what I miss most in linux....the magic trackpad gestures! they are awesome! Then...right click is just two fingers on the pad (i think). The magic mouse looks cool...but in usage is garbage!

I'll be honest....I got them as "toys"...and mostly don't use em daily anymore. Not that they are not capable. I especially like the formfactor of my 11 inch macbook air! I am more of a linux user for nearly 16 years now...and i missed a lot of it. I do LOVE the timeless look of the iMac! Even the 2011 model! It looks so modern....I had it for decoration on my desk for months....hahaha

But, to respond to you're issues. You might want to look into "homebrew", or just brew. It is a package manager for MacOS that can install a lot of linux packages. Then you just do "brew install python3" and it's magically installed and callable from your terminal.

Another option to consider is Docker...so you can run all compilers and dependencies in an isolated container. keeps your macos clean.

Hope that helps a bit. good luck! :)
 
i guess it depends on your mac if you have ethernet ;) I have 4...all "ancients" from 2011-2014. upgraded SSD's and OCLP to make newer macos work on them. I even have Sonoma working on a 2011 iMac :D I even bought the magic trackpad because I liked it on the macbook so much! that's what I miss most in linux....the magic trackpad gestures! they are awesome! Then...right click is just two fingers on the pad (i think). The magic mouse looks cool...but in usage is garbage!

I'll be honest....I got them as "toys"...and mostly don't use em daily anymore. Not that they are not capable. I especially like the formfactor of my 11 inch macbook air! I am more of a linux user for nearly 16 years now...and i missed a lot of it. I do LOVE the timeless look of the iMac! Even the 2011 model! It looks so modern....I had it for decoration on my desk for months....hahaha

But, to respond to you're issues. You might want to look into "homebrew", or just brew. It is a package manager for MacOS that can install a lot of linux packages. Then you just do "brew install python3" and it's magically installed and callable from your terminal.

Another option to consider is Docker...so you can run all compilers and dependencies in an isolated container. keeps your macos clean.

Hope that helps a bit. good luck! :)
problem is, python3 is already installed by default. I can type python3 from the terminal already. I can even type python and it will work, since I made an alias. But when @python is encountered in one of SciresM's .mk files, it doesn't work. It's easy for me to change the 3 files to say @python3 instead, and then there's is no issue. It's just infuriating that I must resort to that.
 
problem is, python3 is already installed by default. I can type python3 from the terminal already. I can even type python and it will work, since I made an alias. But when @python is encountered in one of SciresM's .mk files, it doesn't work. It's easy for me to change the 3 files to say @python3 instead, and then there's is no issue. It's just infuriating that I must resort to that.
You mean you have an "alias" for both python3 and python pointing to the same binary of python3? right? That might be an issue if the expectation is that "python" is python2.x! Python 2 and 3 have a lot of syntax incompatibilities!

You're trying to compile atmosphere-NX right? from github with all the latest updates of devkitpro etc? I have not tried myself....not intterested in building myself. But, i do know how frustrating it is if you want or need to build a thing and it just does not work!

I can highly recommend at least trying to explain your issues to ChatGPT! It has helped me discover issues in building stuff multiple times. Just give it the version numbers of tools you have, that your on mac os, even give it the github link to the repo. It helps if you have the paid version of ChatGPT.
And after that it will give you a bunch of things to try. try them...and feed the errors back saying it did not work! Then it gives new options to try.

If that does not work, or you don't want to, there is always the discord from what I could find in the repository. maybe some real human there can help you out. :D

Good luck.
 
You mean you have an "alias" for both python3 and python pointing to the same binary of python3? right? That might be an issue if the expectation is that "python" is python2.x! Python 2 and 3 have a lot of syntax incompatibilities!

You're trying to compile atmosphere-NX right? from github with all the latest updates of devkitpro etc? I have not tried myself....not intterested in building myself. But, i do know how frustrating it is if you want or need to build a thing and it just does not work!

I can highly recommend at least trying to explain your issues to ChatGPT! It has helped me discover issues in building stuff multiple times. Just give it the version numbers of tools you have, that your on mac os, even give it the github link to the repo. It helps if you have the paid version of ChatGPT.
And after that it will give you a bunch of things to try. try them...and feed the errors back saying it did not work! Then it gives new options to try.

If that does not work, or you don't want to, there is always the discord from what I could find in the repository. maybe some real human there can help you out. :D

Good luck.
On an Ubuntu VM on my windows machine, I use "python is python3", so I Can 100% guarantee there is no compatibility issues building with python3. Not sure why you would suggest that, considering I already stated that I can just alter the .mk files to make it build. It just adds more overhead, because I then need to git stash before I can git pull, when there's an update. Then git stash pop (as long as the changes don't conflict, in which case, I have to manually change the files again).

I have good reason to want to build things myself. I spend at least half of every year out to sea, where I may not be able to download new binaries, because of limited bandwidth (imagine 1 starlink connection for 5,000 people). It is much more possible to pull the git changes, and even then I need to make global changes to the git command to disable timeouts.

And sure, I could go the VM route on the MAC, but I already have a VM on my Windows laptop. Storage on the Mac is limited, so I'd even feel the need to place the VM on an external.
 
Last edited:
On an Ubuntu VM on my windows machine, I use "python is python3", so I Can 100% guarantee there is no compatibility issues building with python3. Not sure why you would suggest that, considering I already stated that I can just alter the .mk files to make it build. It just adds more overhead, because I then need to git stash before I can git pull, when there's an update. Then git stash pop (as long as the changes don't conflict, in which case, I have to manually change the files again).
I only mention it because at least on my ubuntu 20.04 (upgraded from 18.04) the default for "python" is actually Python 2.7.18 and "python3" Python 3.8.10 and it has bitten me in the behind a couple of times when i forgot this! So it was just a friendly reminder that "if" the build scripts would expect "python" to actually point to a python 2.x version it might be a source of errors.
I think i must have read over the bit where you said you had a successful build with the changes in the .mk files. I thought it still did not work after that. my bad! :blush:

I have good reason to want to build things myself. I spend at least half of every year out to sea, where I may not be able to download new binaries, because of limited bandwidth (imagine 1 starlink connection for 5,000 people). It is much more possible to pull the git changes, and even then I need to make global changes to the git command to disable timeouts.
I wasn't judging you in any way for building it yourself, just saying that i did not have personal experience with the atmosphere build process or the need/interest to do so. Starlink at sea...is that still a 100mbit downlink? That's tough with 5000 other users!
But since i do have experience with make on linux...and a limited time as a user on macos....I just thought I would offer some assistance and point out some potential issues. Just be aware of it when changing the name a buildscript calling "python" might expect it to be python 2.x and not python 3.x
If your changes work...great! Then ignore what I said. No offense meant on my part. ^_^
And sure, I could go the VM route on the MAC, but I already have a VM on my Windows laptop. Storage on the Mac is limited, so I'd even feel the need to place the VM on an external.
Yeah, assuming you have a newer macbook the fixed soldered non-upgradable SSD really stinks! As I said I have 4 macs all from the period where this was still an option. But I understand not wanting a big 20+GB VM image on a presumably 256GB internal SSD.

Either way, if it works it works. I only meant to help :)
 

Blog entry information

Author
urherenow
Views
253
Comments
6
Last update

More entries in Personal Blogs

More entries from urherenow

Share this entry

General chit-chat
Help Users
  • No one is chatting at the moment.
    Kirbydogs @ Kirbydogs: @SonicMan44 https://upload.wikimedia.org/wikipedia/en/5/53/Snoopy_Peanuts.png can you make me a...