¿ªÔÆÌåÓý

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

Re: x86-64 compilig

 

On Wed, 8 Jun 2011, Elio Fabri wrote:

I followed your suggestion, and the compiler says
gcc: /usr/X11R6/lib/libXm.a: No such file or directory
Actually there is no libXm.a, neither in /usr/X11R6 nor elsewhere
Hi,

you have to install openmotif-devel, it contains libXm.a. However, the libraries are in /usr/lib now, not in /usr/X11R6/lib anymore.

Saluti,

Michael



P.S.: funny, our offices are in the same building, about 30 meters apart


Re: x86-64 compilig

 

If your Motif's include is in /usr/include and library in /usr/lib64 then try

$ make MOTIFI=/usr/include MOTIFL=/usr/lib64

Good Luck


On Wed, Jun 8, 2011 at 4:32 PM, Elio Fabri <fabri@...> wrote:
I followed your suggestion, and the compiler says
gcc: /usr/X11R6/lib/libXm.a: No such file or directory
Actually there is no libXm.a, neither in /usr/X11R6 nor elsewhere
--
----------------------------------
Elio Fabri
c/o Dip. di Fisica - Univ. di Pisa
----------------------------------


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
? ?

<*> Your email settings:
? ?Individual Email | Traditional

<*> To change settings online go to:
? ?
? ?(Yahoo! ID required)

<*> To change settings via email:
? ?xephem-digest@...
? ?xephem-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
? ?xephem-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
? ?



Re: x86-64 compilig

 

I followed your suggestion, and the compiler says
gcc: /usr/X11R6/lib/libXm.a: No such file or directory
Actually there is no libXm.a, neither in /usr/X11R6 nor elsewhere
--
----------------------------------
Elio Fabri
c/o Dip. di Fisica - Univ. di Pisa
----------------------------------


Re: x86-64 compilig

 

The cause of the problem is, the static libXm included in the xephem package is for 32-bit apps only.
Try built the xephem by just typing 'make' . If you already installed Motif's dev's package, xephem able to be compiled without any problem.


Thank you.

On Tue, Jun 7, 2011 at 4:57 PM, Elio Fabri <fabri@...> wrote:
Hi, I encounter a problem in trying to compile xepehm in my SL5.4 (64
bit) system.
On executing

make MOTIF=../../libXm/linux86

I get a lot of messages. First, many like
make[1]: `libastro.a' is up to date.

Then many lines like
/usr/bin/ld: warning: i386 architecture of input file
`../../libXm/linux86/libXm.a(ArrowB.o)' is incompatible with i386:x86-64
output

The binary xephem is created, but trying to execute ./xephem I get
"segmentation fault".

Can someone help me?
Thx
--
----------------------------------
Elio Fabri
c/o Dip. di Fisica - Univ. di Pisa
----------------------------------


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
? ?

<*> Your email settings:
? ?Individual Email | Traditional

<*> To change settings online go to:
? ?
? ?(Yahoo! ID required)

<*> To change settings via email:
? ?xephem-digest@...
? ?xephem-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
? ?xephem-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
? ?



x86-64 compilig

 

Hi, I encounter a problem in trying to compile xepehm in my SL5.4 (64 bit) system.
On executing

make MOTIF=../../libXm/linux86

I get a lot of messages. First, many like
make[1]: `libastro.a' is up to date.

Then many lines like
/usr/bin/ld: warning: i386 architecture of input file `../../libXm/linux86/libXm.a(ArrowB.o)' is incompatible with i386:x86-64 output

The binary xephem is created, but trying to execute ./xephem I get "segmentation fault".

Can someone help me?
Thx
--
----------------------------------
Elio Fabri
c/o Dip. di Fisica - Univ. di Pisa
----------------------------------


Re: Wayland display server support

Akkana Peck
 

ecdowney2002 writes:
Good ol' linux, always a moving target. If this breaks X11 clients I very much doubt I will have the motivation to chase it.
The rumor is that the X11 protocol will be implemented on top of
Wayland, so Xlib and associated libraries won't need any changes at all.
So I've been told by several Ubuntu people, none of them actually
Wayland or Xlib developers. I haven't seen it written anywhere.
Sounds nice, if it's true!

...Akkana


Re: Wayland display server support

ecdowney2002
 

Good ol' linux, always a moving target. If this breaks X11 clients I very much doubt I will have the motivation to chase it.

--- In xephem@..., "njpcoleman" <jemmyducks@...> wrote:

Wayland is a new display server that is being promoted by Ubuntu and RedHat. It is a complete replacement for X, but will apparently provide backwards compatibility by starting a one-off X instance if an application needs X.

I don't have any bias towards Wayland since I run Slackware, which uses Xorg.

Elwood,have you any thoughts on Wayland and its effect on XEphem? I imagine you would not be looking forward to dealing with it.


Wayland display server support

 

Wayland is a new display server that is being promoted by Ubuntu and RedHat. It is a complete replacement for X, but will apparently provide backwards compatibility by starting a one-off X instance if an application needs X.

I don't have any bias towards Wayland since I run Slackware, which uses Xorg.

Elwood,have you any thoughts on Wayland and its effect on XEphem? I imagine you would not be looking forward to dealing with it.


Re: Miranda ephemeris gone haywire after 1/1/2011?

ecdowney2002
 

RC13 now includes a fix for this issue. Basically the file uranus.1020 was corrupted.

Elwood

--- In xephem@..., "ecdowney2002" <ecdowney@...> wrote:

Hello Piero, thanks for the report. I have confirmed your report on a fresh compile of RC11 on Ubuntu 10.10. I will look into it and update the forum if I learn anything.

Elwood


Re: Old DST rules under Ubuntu 10.10 FIXED

 

--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:
Elwood, Thad:

Thank you for taking the time to investigate the problem. Because
you confirmed that there is no DST problem with XEphem under Ubuntu
10.10, I took another look at it, this time not concentrating on the
C code.

The problem originated because I created a Site Selection. The DST
begin/end dates are part of the created site selection entry, and
default to the old DST. When I selected a nearby site from the
original, unaltered site selection list, then DST works correctly.

I feel much better now.
Now THAT's interesting!

In all the years (many) I've been using XEphem, I've never used the
"Site Selection" window:

<>

What I've always done (because it seemed obvious to me) was simply
include my sites in the "auxil/xephem_sites" file. For example:

[...]
Texarkana, Texas ; 33 25 48 N ; 94 2 30 W ; 98.8 ; CST6CDT
ThadLABS, Los Altos CA ; 37 20 17 N ; 122 4 17 W ; 78.1 ; PST8PDT
Tokyo, Japan ; 35 45 0 N ; 139 45 0 E ; 9.1 ; JST-9
[...]

and that's how/why the main XEphem window on my systems looks like:

<> 25KB

and I never had any problems.


Re: Old DST rules under Ubuntu 10.10 FIXED

Kevin Randolph
 

Elwood, Thad:

Thank you for taking the time to investigate the problem.? Because you confirmed that there is no DST problem with XEphem under Ubuntu 10.10, I took another look at it, this time not concentrating on the C code.

The problem originated because I created a Site Selection.? The DST begin/end dates are part of the created site selection entry, and default to the old DST.? When I selected a nearby site from the original, unaltered site selection list, then DST works correctly.

I feel much better now.

Thanks again,
Kevin


-----Original Message-----
From: Kevin Randolph
To: xephem
Sent: Wed, Mar 23, 2011 11:10 am
Subject: Re: [xephem] Re: Old DST rules under Ubuntu 10.10

?
Elwood, Thad:

Thank you for looking into this matter.

I'm running XEphem Version 3.7.4 July 3, 2009.?

I'll poke around and see if I can figure out what is happening on my system.? I'm glad to hear it is working OK for you guys.

-Kevin


-----Original Message-----
From: ecdowney2002 <ecdowney@...>
To: xephem <xephem@...>
Sent: Wed, Mar 23, 2011 10:22 am
Subject: [xephem] Re: Old DST rules under Ubuntu 10.10

?
Hi Kevin,

FWIW, I'm running Ubuntu 10.10 kernel 2.6.35-28-generic and XEphem changed timezone on March 13 ok for me. I live in Tucson where we don't use DST but I set the location to Chicago and confirmed the offset changes from 6 to 5 hours on Mar 13. I tried both the 3.7.5-RC11 I built on here and the 3.7.4 executable on the commercial edition, both worked ok. This ubuntu is running on Windows XP under VirtualBox 4.0.4. I have done nothing special to administer timezones but I did notice a week or two ago that the normal system updates brought in something related to timezones but I did not watch carefully to know exactly what it did. I admit I tend to pay as little attention as possible to system administration duties. I see some discussion in later posts to this thread about TZ. Note that XEphem does not explicitly use TZ, it performs all timezone calculations based on the difference between localtime() and gmtime() library calls.

I wish I could be more help but at this end I don't see anything to work on.

Regards,

Elwood

--- In xephem@..., Kevin Randolph wrote:
>
> The TZ name indicator appears to use the old DST rules under Ubuntu 10.10.
>
> To verify this, set the current date to early in March, then advance a day at a time while looking at the TZ name indicator. When it reaches the 2nd Sunday in March, it is still indicating standard time. Continuing to advance a day at a time, the TZ name indicator switches to daylight savings time on the first Sunday in April. These are the old DST rules.
>
> I asked Elwood about this. He said that xephem gets its DST info from the OS, which makes sense.
>
> Ubuntu 10.10 does know about correct standard/daylight time as evidenced by the TOD clock and the 'date' shell command.
>
> Can someone running Ubuntu verify this?
>
> Where might I look in the code to try to fix this?
>
> Thanks,
> Kevin
>
>
>
> ------------
> Kevin Randolph
> Kevin@...
> Cell: 216-272-4994
>


Re: Old DST rules under Ubuntu 10.10

Kevin Randolph
 

Elwood, Thad:

Thank you for looking into this matter.

I'm running XEphem Version 3.7.4 July 3, 2009.?

I'll poke around and see if I can figure out what is happening on my system.? I'm glad to hear it is working OK for you guys.

-Kevin


-----Original Message-----
From: ecdowney2002
To: xephem
Sent: Wed, Mar 23, 2011 10:22 am
Subject: [xephem] Re: Old DST rules under Ubuntu 10.10

?
Hi Kevin,

FWIW, I'm running Ubuntu 10.10 kernel 2.6.35-28-generic and XEphem changed timezone on March 13 ok for me. I live in Tucson where we don't use DST but I set the location to Chicago and confirmed the offset changes from 6 to 5 hours on Mar 13. I tried both the 3.7.5-RC11 I built on here and the 3.7.4 executable on the commercial edition, both worked ok. This ubuntu is running on Windows XP under VirtualBox 4.0.4. I have done nothing special to administer timezones but I did notice a week or two ago that the normal system updates brought in something related to timezones but I did not watch carefully to know exactly what it did. I admit I tend to pay as little attention as possible to system administration duties. I see some discussion in later posts to this thread about TZ. Note that XEphem does not explicitly use TZ, it performs all timezone calculations based on the difference between localtime() and gmtime() library calls.

I wish I could be more help but at this end I don't see anything to work on.

Regards,

Elwood

--- In xephem@..., Kevin Randolph wrote:
>
> The TZ name indicator appears to use the old DST rules under Ubuntu 10.10.
>
> To verify this, set the current date to early in March, then advance a day at a time while looking at the TZ name indicator. When it reaches the 2nd Sunday in March, it is still indicating standard time. Continuing to advance a day at a time, the TZ name indicator switches to daylight savings time on the first Sunday in April. These are the old DST rules.
>
> I asked Elwood about this. He said that xephem gets its DST info from the OS, which makes sense.
>
> Ubuntu 10.10 does know about correct standard/daylight time as evidenced by the TOD clock and the 'date' shell command.
>
> Can someone running Ubuntu verify this?
>
> Where might I look in the code to try to fix this?
>
> Thanks,
> Kevin
>
>
>
> ------------
> Kevin Randolph
> Kevin@...
> Cell: 216-272-4994
>


Re: Old DST rules under Ubuntu 10.10

ecdowney2002
 

Hi Kevin,

FWIW, I'm running Ubuntu 10.10 kernel 2.6.35-28-generic and XEphem changed timezone on March 13 ok for me. I live in Tucson where we don't use DST but I set the location to Chicago and confirmed the offset changes from 6 to 5 hours on Mar 13. I tried both the 3.7.5-RC11 I built on here and the 3.7.4 executable on the commercial edition, both worked ok. This ubuntu is running on Windows XP under VirtualBox 4.0.4. I have done nothing special to administer timezones but I did notice a week or two ago that the normal system updates brought in something related to timezones but I did not watch carefully to know exactly what it did. I admit I tend to pay as little attention as possible to system administration duties. I see some discussion in later posts to this thread about TZ. Note that XEphem does not explicitly use TZ, it performs all timezone calculations based on the difference between localtime() and gmtime() library calls.

I wish I could be more help but at this end I don't see anything to work on.

Regards,

Elwood

--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:

The TZ name indicator appears to use the old DST rules under Ubuntu 10.10.

To verify this, set the current date to early in March, then advance a day at a time while looking at the TZ name indicator. When it reaches the 2nd Sunday in March, it is still indicating standard time. Continuing to advance a day at a time, the TZ name indicator switches to daylight savings time on the first Sunday in April. These are the old DST rules.

I asked Elwood about this. He said that xephem gets its DST info from the OS, which makes sense.

Ubuntu 10.10 does know about correct standard/daylight time as evidenced by the TOD clock and the 'date' shell command.

Can someone running Ubuntu verify this?

Where might I look in the code to try to fix this?

Thanks,
Kevin



------------
Kevin Randolph
Kevin@...
Cell: 216-272-4994


Re: Old DST rules under Ubuntu 10.10

 

--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:
[...]
Where might I look in the code to try to fix this?
What is your XEphem version?


Re: Old DST rules under Ubuntu 10.10

 

--- In xephem@..., "thad_floryan" <thad@...> wrote:
[...]
Interesting, XEphem also works correctly on my Vista SP2 system under
Cygwin: <>
Note the "CDT" for 15-MAR-2011.
[...]
And here's the screenshot from my Ubuntu 8.04.4 LTS system:

<>

Note the "PDT" in the TZ Name.


Re: Old DST rules under Ubuntu 10.10

 

--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:

Thad,

Thanks for your response.

Good guess about setting the time zone on my machine, but that is
not the problem. The machine correctly displays time, time zone,
and DST in the TOD clock and 'date' shell command (example: Tue Mar
22 19:49:48 MDT 2011).

XEphem 'TZ name' adheres to the old DST rules for reasons unknown.
The 'TZ offset' is consistent with the 'TZ name' field. It, too,
shows the standard time offset (7:00:00 here in the US Mountain time
zone) until the first Sunday in April, when it decreases by 1 hour
(6:00:00) and the 'TZ name' field changes to 'MDT'.
Puzzling. I just-now fired up my Ubuntu 8.04.4 LTS system upon which
I have XEphem 3.7.3 installed. Following your original example, I set
the date to Sunday, 6-MAR-2011, and the looping to step 24:0:0 and
clicked [Update] repeatedly. On Sunday, 13-MAR-2011 the "TZ Name"
switched from PST (I'm in Silicon Valley) to PDT as it should do.

In other words, XEphem is operating correctly. I don't have a Ubuntu
10.10 system to test this on, but XEphem 3.7.3 is also operating
correctly on my Red Hat 9 system (2003) and my Solaris 10 system. I
have a lot of computers here: <>

Interesting, XEphem also works correctly on my Vista SP2 system under
Cygwin: <>
Note the "CDT" for 15-MAR-2011.

XEphem 'UTC time' is showing the correct UTC time always.
Correect.

I suspect a library function is reporting DST as if it was
determined by the old DST rules. Maybe there is an option to
specify old/new DST rules?
Nothing like that in the Ubuntu date&time URL I posted earlier.

Given how Ubuntu "changes", 10.10 may have a bug. Prior versions
work fine.

What do you mean by 'TZ is not set' in your post?
REGULUS bash 1/2124> echo $TZ

REGULUS bash 1/2124>

"Not set" = "Empty"

I don't recall seeing anything in $TZ since SunOS 4.1.4 back in the
early 1990s.


Re: Old DST rules under Ubuntu 10.10

Kevin Randolph
 

Thad,

Thanks for your response.

Good guess about setting the time zone on my machine, but that is not the problem.? The machine correctly displays time, time zone, and DST in the TOD clock and 'date' shell command (example: Tue Mar 22 19:49:48 MDT 2011).

XEphem 'TZ name' adheres to the old DST rules for reasons unknown.? The 'TZ offset' is consistent with the 'TZ name' field.? It, too, shows the standard time offset (7:00:00 here in the US Mountain time zone) until the first Sunday in April, when it decreases by 1 hour (6:00:00) and the 'TZ name' field changes to 'MDT'.

XEphem 'UTC time' is showing the correct UTC time always.

I suspect a library function is reporting DST as if it was determined by the old DST rules.? Maybe there is an option to specify old/new DST rules?

What do you mean by 'TZ is not set' in your post?

Thanks,
Kevin


-----Original Message-----
From: thad_floryan
To: xephem
Sent: Tue, Mar 22, 2011 7:21 pm
Subject: [xephem] Re: Old DST rules under Ubuntu 10.10

?
--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:
>
> The TZ name indicator appears to use the old DST rules under Ubuntu
> 10.10.
>
> To verify this, set the current date to early in March, then
> advance a day at a time while looking at the TZ name indicator.
> When it reaches the 2nd Sunday in March, it is still indicating
> standard time. Continuing to advance a day at a time, the TZ name
> indicator switches to daylight savings time on the first Sunday in
> April. These are the old DST rules.
>
> I asked Elwood about this. He said that xephem gets its DST info
> from the OS, which makes sense.
>
> Ubuntu 10.10 does know about correct standard/daylight time as
> evidenced by the TOD clock and the 'date' shell command.
>
> Can someone running Ubuntu verify this?
>
> Where might I look in the code to try to fix this?

As best I can determine, TZ hasn't been used in awhile (since at least
Ubuntu 7.10). I have Ubuntu 8.04.4 LTS running XEphem and everything
is fine. TZ is not set.

I have Ubuntu 9.04 on my SheevaPlugs and TZ is not set and everything
is fine.

I just booted a LUBUNTU 10.10 live CD, date and time are all OK and
TZ is not set.

What you want to do is: sudo tzconfig

"sudo dpkg-reconfigure tzdata" should work, too.

More info here:

<>


Re: Old DST rules under Ubuntu 10.10

 

--- In xephem@..., Kevin Randolph <kevin44121@...> wrote:

The TZ name indicator appears to use the old DST rules under Ubuntu
10.10.

To verify this, set the current date to early in March, then
advance a day at a time while looking at the TZ name indicator.
When it reaches the 2nd Sunday in March, it is still indicating
standard time. Continuing to advance a day at a time, the TZ name
indicator switches to daylight savings time on the first Sunday in
April. These are the old DST rules.

I asked Elwood about this. He said that xephem gets its DST info
from the OS, which makes sense.

Ubuntu 10.10 does know about correct standard/daylight time as
evidenced by the TOD clock and the 'date' shell command.

Can someone running Ubuntu verify this?

Where might I look in the code to try to fix this?
As best I can determine, TZ hasn't been used in awhile (since at least
Ubuntu 7.10). I have Ubuntu 8.04.4 LTS running XEphem and everything
is fine. TZ is not set.

I have Ubuntu 9.04 on my SheevaPlugs and TZ is not set and everything
is fine.

I just booted a LUBUNTU 10.10 live CD, date and time are all OK and
TZ is not set.

What you want to do is: sudo tzconfig

"sudo dpkg-reconfigure tzdata" should work, too.

More info here:

<>


Old DST rules under Ubuntu 10.10

Kevin Randolph
 

The TZ name indicator appears to use the old DST rules under Ubuntu 10.10.

To verify this, set the current date to early in March, then advance a day at a time while looking at the TZ name indicator.? When it reaches the 2nd Sunday in March, it is still indicating standard time.? Continuing to advance a day at a time, the TZ name indicator switches to daylight savings time on the first Sunday in April.? These are the old DST rules.

I asked Elwood about this.? He said that xephem gets its DST info from the OS, which makes sense.

Ubuntu 10.10 does know about correct standard/daylight time as evidenced by the TOD clock and the 'date' shell command.

Can someone running Ubuntu verify this?

Where might I look in the code to try to fix this?

Thanks,
Kevin

------------
Kevin Randolph
Kevin@...
Cell: 216-272-4994


Re: Vernal Equinox -- astrometric vs. apparent?

Akkana Peck
 

Brandon Craig Rhodes writes:
When I packaged the XEphem computation routines so that they could be
used by Python programmers, I went ahead and attempted to write up an
explanation of how these coordinates differ. My explanation might not
be very clear - and might even be wrong if there are points of the
science that I misunderstood - but here it is, in case it helps you:

Thanks! That's by far the best explanation I've found. I wrote
a little PyEphem program to watch the three sets of coordinates
change, and convinced myself that was indeed the issue. Also,
next_equinox() is a nice straightforward way to get the exact
time, next time I want to verify it ... much easier than trying
lots of dates by hand in XEphem.

I'm still amazed the difference relativistic deflection + nutation +
aberration of light makes a difference of four hours in the time
of the equinox. I don't suppose PyEphem offers a way to separate out
these effects, by any chance? I'm guessing nutation is the big one in
this case.

...Akkana