Keyboard Shortcuts
Likes
- Xephem
- Messages
Search
Re: XEphem fails on MacOS 10.15.3 with Macports
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, but I fear doing that so I hesitate. I will no doubt kick myself when I get it running for having overlooked the obvious, but meanwhile (well, you get it). |
Re: XEphem fails on MacOS 10.15.3 with Macports
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 args Checking colormap Building icon Building main window system Connecting actions Building main menu bar Warning: Fatal Error:? _XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL Segmentation fault %? |
Re: XEphem fails on MacOS 10.15.3 with Macports
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 different, I think. When we eventually figure this out I don't think it will have turned out to be a big deal. ?Says Mr. Optimism...
|
Re: XEphem fails on MacOS 10.15.3 with Macports
Have you checked your DISPLAY environment variable? On macOS the old favorite :0 does not work. At the moment mine is:
echo $DISPLAY
DISPLAY=/private/tmp/com.apple.launchd.Y3GlPNjYOH/org.macosforge.xquartz:0 This should be set automatically when you log in when xquartx is started by launchd but if not, try looking in /private/tmp for something similar then set it yourself, for example: export DISPLAY=/private/tmp/com.apple.launchd.Y3GlPNjYOH/org.macosforge.xquartz:0
xephem You are running xquartz right? Never use macports x11, that is way out of date, and trying to mix it with xquartz will lead to much grief. Uninstall if you have it then get , or try installing it again anyway in case it is messed up somehow. |
Re: XEphem fails on MacOS 10.15.3 with Macports
xephem could stand to have a network of maintainers to help it over
toggle quoted message
Show quoted text
these problems as libraries and operating systems change over time. I remember in Linux it took some time and fiddling because it uses xprint (I think it was) which has mostly passed out of common usage. It would be a fairly thankless job I think, and I'm not much younger than Elwood. I've never seen OS X, and i don't grok AppleSpeak. On 2/21/20, David Reed <w5sv.dave@...> wrote:
I am seeing failure as well; I get the error message: "can't open display" --
------------- No, I won't call it "climate change", do you have a "reality problem"? - AB1JX Cities are cages built to contain excess people and keep them from cluttering up nature. Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach |
Re: XEphem fails on MacOS 10.15.3 with Macports
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 avail; I am no OS X guru, so detailed suggestions would be welcome. Thanks in advance. |
Re: XEphem fails on MacOS 10.15.3 with Macports
Don't know what's in Macports but the XEphem.app within my original disk1 ?is statically linked and still works fine on Catalina 10.15.3 with xquartz 2.7.11. One caveat is sometimes it helps to get xquartz running first by running something like xlogo before starting xephem.?
|
Re: XEphem fails on MacOS 10.15.3 with Macports
¿ªÔÆÌåÓý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 solution: ? ? Alternatively, these two posts also deal with problems with the same library: ? ? Hopefully that helps? ? Rick ? From: SpikeLightfoot
Sent: February 19, 2020 6:35 AM To: [email protected] Subject: [xephem] XEphem fails on MacOS 10.15.3 with Macports ? 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. ? ? |
XEphem fails on MacOS 10.15.3 with Macports
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. ? |
Re: Script Error when starting XEphem on MacOS
Could the "path to me" thing contain any special characters
toggle quoted message
Show quoted text
that would trigger some kind of Unicode mess in the process ? -- fm
|
Script Error when starting XEphem on MacOS
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 (10.14.6) that I am not aware of that is creating the issue, but maybe someone here is knowledgeable in Apple scripts and can point me to possible error sources or even help me fix this error. Searching for error message on the internet didn't result in anything helpful to me at least. Thanks! RK |
Re: XEphem 3.7.7 live CD?
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 there, pretty efficient. On Dec 5, 2019 7:50 AM, "Mathias Homann" <Mathias.Homann@...> wrote:
|
Re: XEphem 3.7.7 live CD?
¿ªÔÆÌåÓýHi Mathias, Than you very much for your offer, if I can vote; KDE Plasma 5 please Thank you woeimun On Thu, 2019-12-05 at 13:50 +0100, Mathias Homann wrote:
|