Ok guys, I just got back from my Eclipse trip on Wednesday and I think I should have the time to try and fix the issue with KStars supporting previous MacOS versions. I believe the issue was something with QT, Craft, and binary files that were not built with older Mac versions in mind. It might take me a few days to do it, but I will try building from scratch without using the binary cache. I also know Eric has been working very hard to make us some new MacOS Craft recipes since I have been too busy the last few months. When he finishes that, we should be able to get regular MacOS builds going again.
Also Ron M. I can try my Canon camera and see what happens. There could be an issue with libraw, I will check
Read More...
Hi Peter,
Glad to hear it! After a bunch of experimentation on various virtual machines, I think that the issue might have to do with some of the binary files craft builds and maintains on their binary server to make building KDE software on MacOS take less time in craft. I think that there was some kind of significant change in memory addressing or a change in some of the library files on MacOS when Sonoma was released and if you don't specify that you are building for an older MacOS, the binaries are not compatible with an older OS. I found the same error that you found when I tried to run my new build of KStars on any virtual machine older than Sonoma, even Ventura. I then tried building in craft on an older machine thinking that if it was built on that OS, it should work on that OS. But in the middle of the build process, when it was trying to build QT tools, which used some prebuilt binary files, I encountered the same error you found when you tried to run KStars.app. That tells me it was not just the app built on my machine, but one or more of the libraries that were prebuilt by craft. Since I don't have time to dive much further into this at this time, I think for now we need to say the build is just for Sonoma systems.
Thanks for your testing and I am glad you got it working,
Rob
Read More...
I did check, the line of code that caused your error was only added to INDI about 2 years ago it seems. Fortunately, as you observed it was recently added to the MacOS SDK.
Read More...
Ok so that was not it then. New strategy.
I opened my indi project in QT Creator and found MSG_NOSIGNAL in the code of indiserver.cpp. I right clicked on it and said to "Follow Symbol under cursor" and it took me to Socket.h which was in my Xcode sdk in this folder:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h
It is there that this symbol was defined.
#if __DARWIN_C_LEVEL >= 200809L
#define MSG_NOSIGNAL 0x80000 /* do not generate SIGPIPE on EOF */
#endif /* __DARWIN_C_LEVEL */
I checked at the top of the indiserver.cpp file and indeed it says "#include <sys/socket.h>" so this file should be included and the symbol should be defined I would think. Do you have Xcode installed on your machine with the latest SDK?
Read More...
I just did a search of my craft directory. I think this "MSG_NOSIGNAL" might be a part of Boost. Just an idea, it might help to install/reinstall something related to boost first:
cd ~/AstroRoot/craft-root/ ; source ~/AstroRoot/craft-root/craft/craftenv.sh;
craft -vi boost-headers
craft -vi indiserver
Not sure if boost-headers is what you need, but just a thought. I could ask Jasem or someone else, they might know.
Read More...
No, I have never tried Qt6. I don't know that everything supports that yet (such as craft, KStars, build scripts, etc).
The error you got looks a lot like a bug in INDI. Just to see if this helps, you could try this in Terminal:
cd ~/AstroRoot/craft-root/ ; source ~/AstroRoot/craft-root/craft/craftenv.sh;
craft -vi indiserver
See if it is successful. You could also specify which version like this:
craft -vi --target stable indiserver
craft -vi --target master indiserver
Maybe one of them has a bug or maybe some issue with it on your machine. This can probably be fixed.
Read More...
If you are on an Intel machine running Sonoma there should be no problem running the script right now. I ran it a few days ago from scratch. That being said I did make a couple of changes when I found some small issues due to changes in craft and one package. So you might try it now since I fixed those problems. I can’t advise you on setting up an arm/silicon environment since my machine is Intel.
Read More...
I found this just now: forum.qt.io/topic/149842/qt-6-5-2-build-...pdate-to-macos14-sdk. This looks related to the error we encountered running the KStars I build on anything but Sonoma. From this it sounds like the issue is something with the MacOS SDK and linking QT. This is a clue for sure.
Read More...