Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

Hi Richard,

Glad to hear it! You should now be able to have a good build environment!

Read More...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 1 month ago

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...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 2 months ago

You can run Sonoma on a 2012 Mac?

Read More...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 2 months ago

So I do have some Parallels Virtual Machines on my home server and I thought I would just test it out on the older machines. We have been building for a minimum MacOS of 10.15 Catalina for awhile now, ever since craft and qt stopped supporting everything lower than those. You might remember when we had to make that change a couple of years ago. So I started by trying it on 10.15.2, and I just found that I encountered the same error you reported Peter. Then I tried Big Sur and found the same error. I tried Sonoma and found that it worked fine. So something must have changed in the last few months either with MacOS, craft, or QT that is causing this error. I don't think it is anything to do with KStars itself. It is possible I have to change something in the build script due to a change somewhere. First I need to see why even though I told it to build for a minimum of 10.15, why it's not working on anything less than Sonoma.

Read More...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 2 months ago

I always find those MacOS crash reports to be hard to understand and read. If I read it correctly it said it could not find some function in /usr/lib/libc++.1.dylib, which is pretty weird since that is a MacOS system file. This is why I asked you to run it from the command line, it can confirm this, or provide more info

Read More...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 2 months ago

Sorry Peter, I should have been more clear. I meant running it from the Terminal like this:

/Applications/KStars.app/Contents/MacOS/kstars

Just type that and then hit enter. It will put all the output in the terminal and say whatever error happens more clearly and with more context about what is going on. It should look something like this (assuming it starts to launch and assuming you don't have your output going to a text file):

rlancaste@Orion ~ % /Applications/KStars.app/Contents/MacOS/kstars
Call to writableLocation without an application-based location.
org.kde.kstars: Welcome to KStars 3.6.9 Beta
org.kde.kstars: Build: 2024-01-26T20:43:19Z
org.kde.kstars: OS: "osx"
org.kde.kstars: API: "x86_64-little_endian-lp64"
org.kde.kstars: Arch: "x86_64"
org.kde.kstars: Kernel Type: "darwin"
org.kde.kstars: Kernel Version: "23.2.0"
org.kde.kstars: Qt Version: 5.15.12
Starting DBus

From this information I can see the context of what it tried to do before crashing, which can help to figure out why it crashed.

if it doesn't all load and launch properly, it should look more like this:

/Applications/KStars.app/Contents/MacOS/kstars
dyld[43469]: Library not loaded: @rpath/libcfitsio.4.dylib
Referenced from: <6F725553-BA37-37E9-8FE8-14001FC17C57> /Applications/KStars.app/Contents/MacOS/kstars
Reason: tried: '/Applications/KStars.app/Contents/Frameworks/libcfitsio.4.dylib' (no such file), '/Applications/KStars.app/Contents/MacOS/../Frameworks/libcfitsio.4.dylib' (no such file), '/Applications/KStars.app/Contents/Frameworks/libcfitsio.4.dylib' (no such file), '/Applications/KStars.app/Contents/MacOS/../Frameworks/libcfitsio.4.dylib' (no such file)
zsh: abort /Applications/KStars.app/Contents/MacOS/kstars

If you can see it, from this I can tell that the reason it did not launch was because it couldn't find libcfitsio.4.dylib, which I temporarily removed just to cause the error so you can see what information we would probably need to solve your crash.

Read More...

Rob Lancaster replied to the topic 'KStars MacOS 3.6.9 Beta' in the forum. 2 months ago

Certainly not. I built the dmg on an Intel Mac and it runs fine on my machine. The code currently is running on Rosetta for arm/silicon. My Mac is running Sonoma not Catalina. I would not think that is a problem since it is set to build for an older OS. Do you have any more info about the crash? I have been very busy recently and have not had much time. Was it on startup or running a driver? Can you run KStars from the command line to get a little more info?

Read More...