I think Trane and I are experiencing different issues and that is to be expected since we are compiling xephem on vastly different platforms. He is building on MODERN mac equipment probably using the ARM chip and the 17th version of OSX and I am compiling on OLD INTEL macs (at least the newest ones in the lab) running the 12th version of OSX. I am NOT experiencing problems with XQuartz(running 2.6.5) under Lion (the seventh version of osx)(Elcap uses an newer version of xquartz but STILL far from the newest) and lib XP.? Many of the assumptions of the modern MAC owners don't hold true in many cases for me. I can't? in all instances run Brew. I can in some instances run Macports or Port. I seem to have access to openssl-dev libs and header files though the code seems to break now with some of the SSL dependent? calls.? As far as the corrupted makefile debacle goes I may have inadvertently left wordwrap of and the link may have not show the complete statement. I don't think it was ever a problem and probably should be chalked up to my failure to communicate clearly.? For my part the principle difficulty seems to be with getting the code to work with ssl. I believe it can be done but I think I need some direction there. There does seem to be an issue running a modern enough ssl with older G5 Macs though I do hold some hope. The more modern (yet still antique) Intel MACs should work with it. I have run Macports and "ported" SSL and SSL3 over to my mac. when I leave things alone with a -lm lssl in the makefile I get three compiler errors and a break. When I use a $(OLL)/libssl.a? things look far uglier with dozens of SSL related routines not found.? I don't think removing the "hack" in xephem.c has any effect in my case it might again me more useful to the ARM MAC bunch and Big Sur.?
