开云体育

Elwood, thanks for trying to help. ?Yes, I am running xquartz; this all worked in the previous release. it broke with macOS Catalina 10.15.3 I am thinking to remove it all and rebuild from scratch,

Thanks for the suggestion, Elwood. ?For me: % echo $DISPLAY /private/tmp/com.apple.launchd.nupkkTMJpP/org.macosforge.xquartz:0 % % xephem Building shell Reading X resources Checking

For what it's worth, for purposes here I don't think MacOS is much different than Linux, since it's BSD-based and there is a nice X11 distribution available to install seamlessly. ?Windows would be

Have you checked your DISPLAY environment variable? On macOS the old favorite :0 does not work. At the moment mine is: echo

xephem could stand to have a network of maintainers to help it over these problems as libraries and operating systems change over time. I remember in Linux it took some time and fiddling because it

I am seeing failure as well; I get the error message: "can't open display" twice; then it quits... I tried rebuilding it which seemed successful, but same error. I tried previous suggestions to no

MacPorts is MacOS release specific. In general with each release of MacOS, I’ve had to update Xcode, and MacPorts. And as someone else pointed out, you want to make sure your XQuartz is up to

Not so obvious to me! ?But I did reinstall and got the same result.

Just to eliminate the obvious, you did reinstall MacPorts, right?

Thank you for the pointer. ?I've installed it and indeed it works well. ?Sometimes it's best not to try to solve a bunch of problems all at once!

Don't know what's in Macports but the XEphem.app within my original disk1 distro ( https://www.clearskyinstitute.com/xephem/ ) is statically linked and still works fine on Catalina 10.15.3 with

Unfortunately these tricks did not work for me. ?Thanks for the suggestions.

My best guess would be that the Catalina upgrade also upgraded some X11 libs (specifically libXt.6.dylib). I found the following post that while not related directly to XEphem, may provide a

After upgrading to Catalina, XEphem (installed via Macports) fails at runtime: This does not appear to be a Macports problem strictly, as it compiles and installs properly.

I circumvented the issue going a different installation path. I compiled xephem from the sources and followed those installation instructions.

I doubt it since the path is only " /Applications/XEphem.app".

Could the "path to me" thing contain any special characters that would trigger some kind of Unicode mess in the process ? -- fm

Hi, I was able to run XEphem on my Mac, but suddenly I get the following error message when starting it. This normal starting script is suddenly causing the error. Probably some new setting on my Mac

I don't use Windows, just little ARM machines like the Raspberry Pi. Which runs XEphem fine, haven't tried it on a Zero. It was written back in 386 and 486 days, I think there's some Fortran in

Hi Mathias, Than you very much for your offer, if I can vote; KDE Plasma 5 please Thank you woeimun