开云体育

Am 23.11.2017 um 14:40 schrieb lists@... [xephem]: There are ready to use RPM packages for openSUSE and fedora on https://software.opensuse.org/package/xephem?search_term=xephem Cheers Mathias

I for myself use(d) xephem on Ubuntu and Debian using packages provided by http://e2rd.piekielko.pl/debian/ and on ARCH Linux where AUR provides xephem,

I'm getting ready to create a VirtualBox purely for the purpose of running XEphem. Does anybody have any recommendations on what flavor of Linux I should use? I'd like the installation of XEphem to be

Hey, Rick! Great to hear from you. I grew up in Gravenhurst, Ont. (Cottage Country!). You can merge the additional gallery images from the commercial version into a new build by copying over the

Hi trane, Thank you for sharing that! I run an older Mac (G4 iBook 12") and I tried building xephem on my OS X 10.5.8 installation. It failed for some reason (can't recall the error - will have to try

Hi, everybody. FIRST: Let me arrive late to the party and say thank you to Elwood for so many great years of XEphem. I started with XEphem back in 2003 on Linux and then migrated seamlessly over to OS

Using the alternate name for the spectral info looks promising... I'll give it a try.. many thanks

Stars support alternate names, thus you could just put the classification in that way. Or, put the classificaiton as the main name, and let alternate name carry the designation. Then using that edb,

Yes, .edb seems fairly clear, but the semantics of the record structure (field designations) seems fairly rigid... What I was wondering is what would happen if you 'hijacked' one of the fields

Homebrewing .edb files is pretty easy. I did one for the 3c radio catalog. They are ASCII files, just look at a few lines from them, and follow along the documentation. You'll get the hang of it.

Hi there, I am a new user and am very impressed with the comprehensive nature of XEphem.. But having recently got into spectroscopy, I was looking for the full spectral classification of stars. Thus I

"jayctheriot@... [xephem]" <xephem@...> wrote: I am running on an RPM system. The patch solved all the problems I had. Doug. -- Mageia release 5 (Official) for x86_64 running

Is this still a problem? I currently have it running on 16.04.x LTS and 16.10. I had to build the missing libraries from scratch, but it runs perfectly. I've got the ability to build debs and post

I've explained it in a former post, here it comes again: The right striplevel for the -p option when applying the openssl patch is dependend from the current working directory relative to the location

Hello I have never patched anything before. So, a step by step description of what to do would be appreciated. The man pages have so many options that they are useless to me. I only require help for

The right striplevel for the -p option when applying the openssl patch is dependend from the current working directory relative to the location of the source files. If you stay in the GUI/xephem

Hi, most likely this o is the one you provided on the command line :) Try patch -p0 instead of -po. -- Fran?ois Meyer

I got the patch file and changed protections in GUI/xephem to be writable. Then, patch: **** strip count o is not a number. > It's curious because of course 'o' is not '0'. What's going on?

Glad to hear it Rick. I haven't used "patch" for years, so I am a bit rusty. I think that what I should have done is go up one folder, to GUI/ and typed "patch -p1." I have always used "patch -p1" in

Hi Doug, Brilliant! That did the trick! Thank you very much. I recompiled, and now I can download the SOHO images. Beauty! Rick