¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Magnitude problem

Santiago Roland
 

Ok, i downloaded the Lowell dim catalog, but i still have the mag 3
asteroid thing using the Unusual from the MPC, maybe the address for
download is bad? I tried to download it again with no luck

Will appreciate any help.


Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------

El 19/11/14 a las 19:46, Santiago Roland santiago@... [xephem]
±ð²õ³¦°ù¾±²ú¾±¨®:



I downloaded the latest files from MPC (the links are shown in the
screenshot), maybe they were not updates properly? I also hit the
download button for Lowell and AstMPC_dim... will try again...

Best regards,

Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------

El 12/11/14 a las 02:40, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:


Like it says, your ephemerides are out of date, which means the
location, and hence magnitudes, for your object are unreliable.


I just downloaded the latest elements from Lowell and 2010 OU100 is
reported as being magnitude 21.7.


Re: Star Catalogs

 

On 11/19/2014 04:42 PM, Santiago Roland santiago@... [xephem] wrote:
Where i can download xephem friendly star catalogues for astrometry? I
would like to download USNO B1, UCAC 4, maybe NOMAD catalog... are those
compatible with xephem? I've been using USNO A2.0 for many years but i
need to upgrade...
Neither USNO B1 nor NOMAD are available for download, they
are too large.

To get a copy of UCAC4 send email to
brenda.hicks@... with a subject
line of UCAC4.


Re: Magnitude problem

Santiago Roland
 

I downloaded the latest files from MPC (the links are shown in the
screenshot), maybe they were not updates properly? I also hit the
download button for Lowell and AstMPC_dim... will try again...

Best regards,


Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------

El 12/11/14 a las 02:40, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:


Like it says, your ephemerides are out of date, which means the
location, and hence magnitudes, for your object are unreliable.


I just downloaded the latest elements from Lowell and 2010 OU100 is
reported as being magnitude 21.7.


Star Catalogs

Santiago Roland
 

Where i can download xephem friendly star catalogues for astrometry? I
would like to download USNO B1, UCAC 4, maybe NOMAD catalog... are those
compatible with xephem? I've been using USNO A2.0 for many years but i
need to upgrade...

Thanks,

--
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------


Re: build steps for cygwin

 

It did indeed work Mike.
Thanks


Re: Magnitude problem

 

Like it says, your ephemerides are out of date, which means the location, and hence magnitudes, for your object are unreliable.

I just downloaded the latest elements from Lowell and 2010 OU100 is reported as being magnitude 21.7.


Re: build steps for cygwin

Mike Mayer
 

¿ªÔÆÌåÓý

Here¡¯s what¡¯s in my Makefile at line 39. I was able to compile 3.7.6 a year ago or so. I think this was the only change I made:

?

#XLIBS = -lXm -lXp -lXt -lXext -lXmu -lX11

XLIBS = -lXm -lXt -lXext -lXmu -lX11

?

==================================================================

Mike Mayer

mwmayer@...

?

From: xephem@... [mailto:xephem@...]
Sent: Tuesday, November 11, 2014 3:37 PM
To: xephem@...
Subject: [xephem] build steps for cygwin

?




I ahve noticed building with more modern versions of cygwin seem more problematic. It wasn't easy to begin with. I have compiled xephem on bewildering array of platforms but find the cygwin one to be the most challenging. The usual culprits seem to be the core of the problem (the motif libraries). On older versions of cygwin I could cajole it into compiling. My experience with the current 64-bit and 32-bit versions are less successful. There was a pretty good cookbook approach to doing this with older versions.

This url worked well in the past.

I think it is an outdated procedure. Could someone work up a new one?

My problem seems to be with the library Xp at least that is where it is hanging up.

Cygwin (bless their geeky little hearts and pointed heads) has changed their directory layouts around tremendously since the old instructions.

-Dr. Karl Oestreich





build steps for cygwin

 

I ahve noticed building with more modern versions of cygwin seem more problematic. It wasn't easy to begin with. I have compiled xephem on bewildering array of platforms but find the cygwin one to be the most challenging. The usual culprits seem to be the core of the problem (the motif libraries). On older versions of cygwin I could cajole it into compiling. My experience with the current 64-bit and 32-bit versions are less successful. There was a pretty good cookbook approach to doing this with older versions.
This url worked well in the past.

I think it is an outdated procedure. Could someone work up a new one?
My problem seems to be with the library Xp at least that is where it is hanging up.
Cygwin (bless their geeky little hearts and pointed heads) has changed their directory layouts around tremendously since the old instructions.
-Dr. Karl Oestreich


Magnitude problem

Santiago Roland
 

Hi guys, i'm having an odd magnitude problem in XEphem. We own an
ordered copy of XEphem 3.7.1 (including the catalog CDs) and some faint
asteroids show as 2 or 3-ish magnitude. I updated the version of XEphem
packaged for Debian distros from this site
() and the error remains unchanged. I
attach a screenshot of my problem so you can help me out. I'm trying to
compile now the version following this tutorial
()

P.S: I compiled RC 3.7.7 and i have the same...

Any help would be great!

Cheers,

--
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------


Re: Yosemite Broke XEphem

 

All,

I've tried the two changes I posted last week now on three systems and they always work. So that appears to be pretty good solution. Again:

to run a pre-Yosemite executable:

? sudo ln -s /opt/X11 /usr

and to build a new one from source follow the instructions in INSTALL but first:

? change the two Makefile lines as per my post on Oct 18 in this thread.


Thanks for using XEphem.

Elwood


Re: Yosemite Broke XEphem

 

¿ªÔÆÌåÓý

that one *should* be easy to resolve:? use the command
??? locate Intrinsic.h
(or whichever way you prefer on a mac) and adjust your Makefile where it is.

I had the /opt/X11 experience already with a 10.9 release.? It baffles me how
AppleInc just randomly decides to deprecate established conventions, but
then again, it's apple. I think we have far worse things coming for developers.
I'm still sticking it out on linux for the time being.

On 10/18/2014 03:31 PM, ngc6352@... [xephem] wrote:

?

Compile of 3.7.6 errors out, unable to find an include file.


../../libXm/osx/Xm/Xm.h:65:10: fatal error: 'X11/Intrinsic.h' file not found

#include


I think I'll wait on Elwood's answer. ?The paths for Yosemite could be seriously different.

Steve
Boise



Re: Yosemite Broke XEphem

 

I tried it in a fresh folder and it failed with the following:

ar rc libz.a adler32.o compress.o crc32.o uncompr.o deflate.o trees.o zutil.o inflate.o inftrees.o inffast.o

ranlib libz.a

gcc -I../../libastro -I../../libip -I../../liblilxml -I../../libjpegd -I../../libpng -I../../libz -g -O2 -Wall -I../../libXm/osx -I/usr/X11R6/include ? -c -o aavso.o aavso.c

In file included from aavso.c:12:

../../libXm/osx/Xm/Xm.h:65:10: fatal error: 'X11/Intrinsic.h' file not found

#include

?? ? ? ? ^

1 error generated.

make: *** [aavso.o] Error 1


I guess there is an issue.


Chris?


On Sat, Oct 18, 2014 at 2:05 PM, Chris Maness <chris@...> wrote:
Did you download a fresh image? You might have stale paths in an old macro.

Chris?

On Sat, Oct 18, 2014 at 12:31 PM, ngc6352@... [xephem] <xephem@...> wrote:


Compile of 3.7.6 errors out, unable to find an include file.

../../libXm/osx/Xm/Xm.h:65:10: fatal error: 'X11/Intrinsic.h' file not found

#include


I think I'll wait on Elwood's answer.? The paths for Yosemite could be seriously different.

Steve
Boise






Re: Yosemite Broke XEphem

 

Did you download a fresh image? You might have stale paths in an old macro.

Chris?

On Sat, Oct 18, 2014 at 12:31 PM, ngc6352@... [xephem] <xephem@...> wrote:


Compile of 3.7.6 errors out, unable to find an include file.

../../libXm/osx/Xm/Xm.h:65:10: fatal error: 'X11/Intrinsic.h' file not found

#include


I think I'll wait on Elwood's answer.? The paths for Yosemite could be seriously different.

Steve
Boise





Re: Yosemite Broke XEphem

 

Compile of 3.7.6 errors out, unable to find an include file.

../../libXm/osx/Xm/Xm.h:65:10: fatal error: 'X11/Intrinsic.h' file not found

#include <X11/Intrinsic.h>


I think I'll wait on Elwood's answer. ?The paths for Yosemite could be seriously different.

Steve
Boise


Re: Yosemite Broke XEphem

 

Compile it from scratch.? Just read the readme file and install Xcode from the app store.? It is free, and installs all your compiler doo-dads.

Chris

On Sat, Oct 18, 2014 at 10:47 AM, ngc6352@... [xephem] <xephem@...> wrote:


I tried a reinstall from the 3.7.2 disks and now I'm totally screwed.? It overwrote the original
app and errored out of the installation before completing the app install.

Oh well.? Guess I'll be without xephem for a while.

Steve
Boise




Re: Yosemite Broke XEphem

 

I tried a reinstall from the 3.7.2 disks and now I'm totally screwed. ?It overwrote the original
app and errored out of the installation before completing the app install.

Oh well. ?Guess I'll be without xephem for a while.

Steve
Boise


Re: Yosemite Broke XEphem

 

Yes, Yosemite moved the X11 libs. XEphem executables built prior to upgrading looks for X11 libraries in /usr/X11. It seems they are now in /opt/X11 but I am not sure yet how universal that will be. If you use macports, they are in /opt/local/lib. So you might have to poke around a little. When you find them, to make your existing executable work, you can make a symlink. For example, XEphem worked for me again after I typed the following in a Terminal:

sudo ln -s /opt/X11 /usr


If you build fresh from source, things get easier in the sense that your result will use the proper location, but it gets worse because the Makefile that ships with the source tarball needs to be adjusted. Change the two lines from


CFLAGS = $(LIBINC) $(CLDFLAGS) -O2 -Wall -I$(MOTIFI) -I/usr/X11R6/include

LDFLAGS = $(LIBLNK) $(CLDFLAGS) -L$(MOTIFL) -L/usr/X11R6/lib


to


CFLAGS = $(LIBINC) $(CLDFLAGS) -O2 -Wall -I$(MOTIFI) -I/opt/X11/include

LDFLAGS = $(LIBLNK) $(CLDFLAGS) -L$(MOTIFL) -L/opt/X11/lib


(or, again, where ever you found the .h and .dylib files)

I did confirm that the libXm.a that ships with the tarball does still work on Yosemite.

I'll post as I figure out more. Sorry for the hassles.

Thanks for using XEphem.

Elwood



Re: Yosemite Broke XEphem

 

I am running Xephem through macports and a build that was compiled for Mavricks.? They both are running fine after an upgrade to Yosemite I just finished a few minutes ago.? Recompile, and give it a go.

Chris?

On Fri, Oct 17, 2014 at 3:22 PM, Dan Frezza dan@... [xephem] <xephem@...> wrote:


Steve,

I updated last night and checked and didn't have a problem. Xephem 3.77-RC3.

Dan


On 10/17/14 4:47 PM, ngc6352@... [xephem] wrote:
?

I just upgraded to Yosemite and it broke XEphem. ?It looks like a path problem and

I suspect Apple changed some directory names, ... . ?I have no idea where to start.


Thanks,

Steve Bell

Boise, ID






Re: Yosemite Broke XEphem [1 Attachment]

Dan Frezza
 

¿ªÔÆÌåÓý

Steve,

I updated last night and checked and didn't have a problem. Xephem 3.77-RC3.

Dan


On 10/17/14 4:47 PM, ngc6352@... [xephem] wrote:

?

I just upgraded to Yosemite and it broke XEphem. ?It looks like a path problem and

I suspect Apple changed some directory names, ... . ?I have no idea where to start.


Thanks,

Steve Bell

Boise, ID



Yosemite Broke XEphem

 

I just upgraded to Yosemite and it broke XEphem. ?It looks like a path problem and

I suspect Apple changed some directory names, ... . ?I have no idea where to start.


Thanks,

Steve Bell

Boise, ID