Bug 61585

Subject: Re:  New: Unlisted dependency - /usr/lib/libfam.la

Hello,

"libfam" or "fam" has been listed as a dependency since 29 March 2002, in the 
file INSTALL.  It's bad that configure doesn't seem to check for libfam, and 
that the compilation fails only at the end.  That's out of our hands, though; 
it's a KDE-autoconf problem.

regards,
Jason

On Wednesday 23 July 2003 01:11 pm, you wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=61585
>            Summary: Unlisted dependency - /usr/lib/libfam.la
>            Product: kstars
>            Version: unspecified
>           Platform: Compiled Sources
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: wishlist
>           Priority: NOR
>          Component: general
>         AssignedTo: kstars@30doradus.org
>         ReportedBy: cj_chitwood@bellsouth.net
>
>
> Version:           CVS as well as 0.9.0 (using KDE KDE 3.1)
> Installed from:    Compiled From Sources
> Compiler:          g++ 3.2.2 as packaged with Mandrake 9.1 Standard
> OS:          Linux
>
> Wish/suggestion for better dependencies list/add a dependency:  I verified
> I had the dependencies listed via the "rpm -qa | grep <dependency name>"
> and all dependencies listed on your website (what, 4 of them? 5?) were
> already installed as RPM packages.  However, after 2 hours of compiling
> kstars, the make (kstars compile, step 7, compiling only kstars (not the
> whole kdeedu thing)) fails with "cannot find the library
> `/usr/lib/libfam.la'".  There is no mention of this requirement in the docs
> I saw online prior to download.  This happened in both 0.9.0 and the latest
> CVS (unsure what that ver # is).  I saw back at rpmfind that I can search
> for individual libraries, so that's my next intention, but it would be nice
> if this dependency was listed ahead of time or perhaps if the file was
> included in the tarball.  OTOH, if I find that the file is part of a listed
> dependency, I'll see what version I have and compare it to what's online
> and update this report. ----------------
> All files I have in relation to this, save for Kstars itself, came from the
> Mandrake Linux 9.1 Standard CDs as shipped by www.CheapBytes.com.  KDE is
> version 3.1.0, kernel is version 2.4.21-0.13mdk#1, compiler is g++ 3.2.2,
> and I have had this problem in both kstars src tarball (I forget what
> version, but I had rpm of version 0.9.0 which worked fine) and the CVS that
> is currently downloadable from edu.kde.org.  I am compiling only kstars,
> NOT the entire kdeedu package (I wanted a planetarium program to run on a
> laptop that can control my Meade ETX-90ec (LX-200 compatible) autostar).
>
> Thanks!  Aside from this, I /did/ try an RPM for redhat 8 that I found at
> rpmfind (I think - it was a google'd link), and it worked fine.  I like the
> program, but I wanted the latest menus and toolbars and such.  I'm used to
> the interface of Starry Night (from Meade), so if the new one is similar,
> that will be a major plus.  I like the sky layout better in kstars, though.

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

Wow, that was quick ;-)

Thanks for the reply...  I was about to update my wish report;  apparently 
it's not libfam it needs but *libfam-devel*.  I downloaded that, and it 
finished the make process.  I'm off to try compiling the handbook and then 
it's time to run it and see what happens.

Thanks again for your time...  and I'm sure I'll be duly impressed once I run 
this version.

CJ

Quoting kstars@30doradus.org from Wednesday 23 July 2003 01:20 pm:
> ]------- You are receiving this mail because: -------
> ]You reported the bug, or are watching the reporter.
> ]
> ]http://bugs.kde.org/show_bug.cgi?id=61585
> ]kstars@30doradus.org changed:
> ]
> ]           What    |Removed                     |Added
> ]--------------------------------------------------------------------------
>-- ]             Status|UNCONFIRMED                 |RESOLVED
> ]         Resolution|                            |FIXED
> ]
> ]
> ]
> ]------- Additional Comments From kstars@30doradus.org  2003-07-23 19:20
> ------- ]Subject: Re:  New: Unlisted dependency - /usr/lib/libfam.la
> ]
> ]Hello,
> ]
> ]"libfam" or "fam" has been listed as a dependency since 29 March 2002, in
> the ]file INSTALL.  It's bad that configure doesn't seem to check for
> libfam, and ]that the compilation fails only at the end.  That's out of our
> hands, though; ]it's a KDE-autoconf problem.
> ]
> ]regards,
> ]Jason
> ]
> ]On Wednesday 23 July 2003 01:11 pm, you wrote:
> ]> ------- You are receiving this mail because: -------
> ]> You are the assignee for the bug, or are watching the assignee.
> ]>
> ]> http://bugs.kde.org/show_bug.cgi?id=61585
> ]>            Summary: Unlisted dependency - /usr/lib/libfam.la
> ]>            Product: kstars
> ]>            Version: unspecified
> ]>           Platform: Compiled Sources
> ]>         OS/Version: Linux
> ]>             Status: UNCONFIRMED
> ]>           Severity: wishlist
> ]>           Priority: NOR
> ]>          Component: general
> ]>         AssignedTo: kstars@30doradus.org
> ]>         ReportedBy: cj_chitwood@bellsouth.net
> ]>
> ]>
> ]> Version:           CVS as well as 0.9.0 (using KDE KDE 3.1)
> ]> Installed from:    Compiled From Sources
> ]> Compiler:          g++ 3.2.2 as packaged with Mandrake 9.1 Standard
> ]> OS:          Linux
> ]>
> ]> Wish/suggestion for better dependencies list/add a dependency:  I
> verified ]> I had the dependencies listed via the "rpm -qa | grep
> <dependency name>" ]> and all dependencies listed on your website (what, 4
> of them? 5?) were ]> already installed as RPM packages.  However, after 2
> hours of compiling ]> kstars, the make (kstars compile, step 7, compiling
> only kstars (not the ]> whole kdeedu thing)) fails with "cannot find the
> library
> ]> `/usr/lib/libfam.la'".  There is no mention of this requirement in the
> docs ]> I saw online prior to download.  This happened in both 0.9.0 and
> the latest ]> CVS (unsure what that ver # is).  I saw back at rpmfind that
> I can search ]> for individual libraries, so that's my next intention, but
> it would be nice ]> if this dependency was listed ahead of time or perhaps
> if the file was ]> included in the tarball.  OTOH, if I find that the file
> is part of a listed ]> dependency, I'll see what version I have and compare
> it to what's online ]> and update this report. ----------------
> ]> All files I have in relation to this, save for Kstars itself, came from
> the ]> Mandrake Linux 9.1 Standard CDs as shipped by www.CheapBytes.com. 
> KDE is ]> version 3.1.0, kernel is version 2.4.21-0.13mdk#1, compiler is
> g++ 3.2.2, ]> and I have had this problem in both kstars src tarball (I
> forget what ]> version, but I had rpm of version 0.9.0 which worked fine)
> and the CVS that ]> is currently downloadable from edu.kde.org.  I am
> compiling only kstars, ]> NOT the entire kdeedu package (I wanted a
> planetarium program to run on a ]> laptop that can control my Meade
> ETX-90ec (LX-200 compatible) autostar). ]>
> ]> Thanks!  Aside from this, I /did/ try an RPM for redhat 8 that I found
> at ]> rpmfind (I think - it was a google'd link), and it worked fine.  I
> like the ]> program, but I wanted the latest menus and toolbars and such. 
> I'm used to ]> the interface of Starry Night (from Meade), so if the new
> one is similar, ]> that will be a major plus.  I like the sky layout better
> in kstars, though. ]

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

Yes, the INSTALL file specifies that you need both the package and its 
"-devel" variant installed for each listed dependency :)

Good luck,
Jason

On Wednesday 23 July 2003 01:24 pm, you wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=61585
>
>
>
>
> ------- Additional Comments From cj_chitwood@bellsouth.net  2003-07-23
> 19:24 ------- Subject: Re:  Unlisted dependency - /usr/lib/libfam.la
>
> Wow, that was quick ;-)
>
> Thanks for the reply...  I was about to update my wish report;  apparently
> it's not libfam it needs but *libfam-devel*.  I downloaded that, and it
> finished the make process.  I'm off to try compiling the handbook and then
> it's time to run it and see what happens.
>
> Thanks again for your time...  and I'm sure I'll be duly impressed once I
> run this version.
>
> CJ
>
> Quoting kstars@30doradus.org from Wednesday 23 July 2003 01:20 pm:
> > ]------- You are receiving this mail because: -------
> > ]You reported the bug, or are watching the reporter.
> > ]
> > ]http://bugs.kde.org/show_bug.cgi?id=61585
> > ]kstars@30doradus.org changed:
> > ]
> > ]           What    |Removed                     |Added
> > ]------------------------------------------------------------------------
> >-- -- ]             Status|UNCONFIRMED                 |RESOLVED
> > ]         Resolution|                            |FIXED
> > ]
> > ]
> > ]
> > ]------- Additional Comments From kstars@30doradus.org  2003-07-23 19:20
> > ------- ]Subject: Re:  New: Unlisted dependency - /usr/lib/libfam.la
> > ]
> > ]Hello,
> > ]
> > ]"libfam" or "fam" has been listed as a dependency since 29 March 2002,
> > in the ]file INSTALL.  It's bad that configure doesn't seem to check for
> > libfam, and ]that the compilation fails only at the end.  That's out of
> > our hands, though; ]it's a KDE-autoconf problem.
> > ]
> > ]regards,
> > ]Jason
> > ]
> > ]On Wednesday 23 July 2003 01:11 pm, you wrote:
> > ]> ------- You are receiving this mail because: -------
> > ]> You are the assignee for the bug, or are watching the assignee.
> > ]>
> > ]> http://bugs.kde.org/show_bug.cgi?id=61585
> > ]>            Summary: Unlisted dependency - /usr/lib/libfam.la
> > ]>            Product: kstars
> > ]>            Version: unspecified
> > ]>           Platform: Compiled Sources
> > ]>         OS/Version: Linux
> > ]>             Status: UNCONFIRMED
> > ]>           Severity: wishlist
> > ]>           Priority: NOR
> > ]>          Component: general
> > ]>         AssignedTo: kstars@30doradus.org
> > ]>         ReportedBy: cj_chitwood@bellsouth.net
> > ]>
> > ]>
> > ]> Version:           CVS as well as 0.9.0 (using KDE KDE 3.1)
> > ]> Installed from:    Compiled From Sources
> > ]> Compiler:          g++ 3.2.2 as packaged with Mandrake 9.1 Standard
> > ]> OS:          Linux
> > ]>
> > ]> Wish/suggestion for better dependencies list/add a dependency:  I
> > verified ]> I had the dependencies listed via the "rpm -qa | grep
> > <dependency name>" ]> and all dependencies listed on your website (what,
> > 4 of them? 5?) were ]> already installed as RPM packages.  However, after
> > 2 hours of compiling ]> kstars, the make (kstars compile, step 7,
> > compiling only kstars (not the ]> whole kdeedu thing)) fails with "cannot
> > find the library
> > ]> `/usr/lib/libfam.la'".  There is no mention of this requirement in the
> > docs ]> I saw online prior to download.  This happened in both 0.9.0 and
> > the latest ]> CVS (unsure what that ver # is).  I saw back at rpmfind
> > that I can search ]> for individual libraries, so that's my next
> > intention, but it would be nice ]> if this dependency was listed ahead of
> > time or perhaps if the file was ]> included in the tarball.  OTOH, if I
> > find that the file is part of a listed ]> dependency, I'll see what
> > version I have and compare it to what's online ]> and update this report.
> > ----------------
> > ]> All files I have in relation to this, save for Kstars itself, came
> > from the ]> Mandrake Linux 9.1 Standard CDs as shipped by
> > www.CheapBytes.com. KDE is ]> version 3.1.0, kernel is version
> > 2.4.21-0.13mdk#1, compiler is g++ 3.2.2, ]> and I have had this problem
> > in both kstars src tarball (I forget what ]> version, but I had rpm of
> > version 0.9.0 which worked fine) and the CVS that ]> is currently
> > downloadable from edu.kde.org.  I am compiling only kstars, ]> NOT the
> > entire kdeedu package (I wanted a planetarium program to run on a ]>
> > laptop that can control my Meade ETX-90ec (LX-200 compatible) autostar).
> > ]>
> > ]> Thanks!  Aside from this, I /did/ try an RPM for redhat 8 that I found
> > at ]> rpmfind (I think - it was a google'd link), and it worked fine.  I
> > like the ]> program, but I wanted the latest menus and toolbars and such.
> > I'm used to ]> the interface of Starry Night (from Meade), so if the new
> > one is similar, ]> that will be a major plus.  I like the sky layout
> > better in kstars, though. ]

AFAIK, fam/libfam is an *optional* depedancy, chosen at build-time of kdelibs. 

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

> ------- Additional Comments From rdieter@math.unl.edu  2003-07-23 21:30
> ------- AFAIK, fam/libfam is an *optional* depedancy, chosen at build-time
> of kdelibs.

If that's true, then why did the bug reporter's compilation of KStars fail at 
the linker stage with "cannot find the library `/usr/lib/libfam.la'" 
(assuming his KDE installation isn't borked)?   The KDE build system seems to 
expect that it is there, seemingly without even checking for it with 
configure.  Very odd.  (BTW, this isn't the first time I've heard of a 
fam-related problem like this).

Jason

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

Quoting rdieter@math.unl.edu  2003-07-23 21:30:
> ]> AFAIK, fam/libfam is an *optional* depedancy, chosen at
> ]> build-time of kdelibs.

Quoting kstars@30doradus.org from Wednesday 23 July 2003 03:38 pm:
> ]If that's true, then why did the bug reporter's compilation of KStars fail
> ]at the linker stage with "cannot find the library `/usr/lib/libfam.la'"
> ](assuming his KDE installation isn't borked)?   

This is the installation as Mandrake's downloadable ISOs have it.  I haven't 
experienced any other distros except RedHat 6.2 (a few years ago, yes ;-)) so 
I can't really say if Mandrake has a standard install of KDE or not.

If it matters, I /did/ install KDE, and used to use it a lot, but wanted to 
play with other things (especially since this AMD K6-2/300 is so slow), so I 
am using WindowMaker almost exclusively.  My shell is Bash, running in 
Konsole.

> ]The KDE build system seems
> ]to expect that it is there, seemingly without even checking for it with
> ]configure.  Very odd.  (BTW, this isn't the first time I've heard of a
> ]fam-related problem like this).

This is only the second time I've contacted anyone about bugs, so this 
actually is a comfort to me ;-)

Unfortunately, I have a pretty standard install.  It came from CheapBytes.com 
(a buddy about 1500 miles away bought and shipped it to me without my desire 
for him to do so), so whatever is on Mandrake's ISO downloads, that's what 
I've got here.

FW little bit IW, I can usually (95% of the time?) get a compilation to work.  
I downloaded this CVS around 9:00 a.m. EDT or so, IIRC, and it wasn't until 
ten minutes ago that the program finally ran (4:00 p.m. EDT).  Only about 2 
and a half hours were spent compiling (granted, I was doing some stuff online 
for college while I waited).  The rest was spent trying to figure this thing 
out.  

After finally getting everything compiled (just needed all the files available 
and with right modes), I had the problem with it not finding the files it 
wanted (specifically, "TZrules.dat", "Cities.dat", "saoN.<png?>") and I wound 
up just copying the whole /usr/share/apps/kstars/data directory's contents 
into /usr/share/apps/kstars (this was because all the files it was asking for 
were in the same directory, needed in the same different directory, so the 
copy was obvious).  I overwrote all, and then the thing worked.  I had tried 
this before, but I must have been in the wrong directory, as it didn't work 
before.

Regardless, I just have gotten it working and so far I'm pleased.  Worth the 
effort?  Not really, but I am impatient and hate waiting for RPMs ;-)

Besides, I might have learned something.

Back to the past, I want to let Jason know I'm not crazy ;-).  I had said in 
the initial report that I had all the dependencies.  According to 
http://edu.kde.org/kstars/handbook/requirements.html specifically, I did.  
What I /didn't/ know was that the INSTALL file was /also/ available online 
(found this out after some more exploring).  I read it once, and totally 
missed that dependency (horizontal scrollbar...  who'da thunk it?), and then 
I saw it after the second read.  He is indeed correct, the dependency upon 
/several/ files is specifically noted in the INSTALL, and the one I was 
missing was amongst them.

I guess this isn't an often-seen problem since the dep list isn't in an easier 
to get to spot, so I'm not worried about it if you guys aren't.  (and by 
easier-to-get-to, you might find it worthy to note that this is the -first- 
CVS program I have tried, so my UberNubity could have played an important 
factor in all of this, since I don't know if there is some kind of set ritual 
that an experienced CVSer follows...)

Anyway, I've been so wrapped up in this, I've yet to get my shower, lol, so 
I'm going to go do that and then hook my scope up and see what it can do.  If 
all works well, I'll go through all this on the laptop (a much faster 
Pentium-III 900) and set it up there.  Then it's just a matter of waiting for 
the right evening sky clarity.

Just a note, has anyone noticed any issues that I should concern myself with 
in connecting this to an LX200-compatible ETX-90ec?

Thanks again, guys, and sorry for the long reply...

CJ

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

Hi CJ,

> Back to the past, I want to let Jason know I'm not crazy ;-).  I had said
> in the initial report that I had all the dependencies.  According to
> http://edu.kde.org/kstars/handbook/requirements.html specifically, I did.
> What I /didn't/ know was that the INSTALL file was /also/ available online
> (found this out after some more exploring).  I read it once, and totally
> missed that dependency (horizontal scrollbar...  who'da thunk it?), and
> then I saw it after the second read.  He is indeed correct, the dependency
> upon /several/ files is specifically noted in the INSTALL, and the one I
> was missing was amongst them.
>
Well, the INSTALL file is included with the code when you download either a 
release tarball or CVS.  We didn't mean to hide it, promise!  Actually, 
distributing an INSTALL file with installation instructions is pretty 
standard procedure for Free software.  (out of curiosity, where did you find 
the INSTALL file online? webcvs.kde.org?)

Thank you for letting us know that the Handbook list of requirements is 
incomplete, though.  I'll update that right away.

> Just a note, has anyone noticed any issues that I should concern myself
> with in connecting this to an LX200-compatible ETX-90ec?
>
None that I know of.  Please do let us know of your experiences using the 
telescope control stuff.  It's brand-new code and we have as yet gotten no 
user feedback about it.

Clear skies,
Jason

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

> ]------- Additional Comments From kstars@30doradus.org  2003-07-23 22:37
> ------- ]Subject: Re:  Unlisted dependency - /usr/lib/libfam.la
> ]
> ]Hi CJ,
> ]
> ]Well, the INSTALL file is included with the code when you download either
> ]a release tarball or CVS.  We didn't mean to hide it, promise!  Actually,
> ]distributing an INSTALL file with installation instructions is pretty
> ]standard procedure for Free software.  (out of curiosity, where did you
> ]find the INSTALL file online? webcvs.kde.org?)

Yes, that I've learned.  I've compiled a lot of stuff, fairly easy thing to 
do, really.  However, I try to check dependencies of larger programs before I 
DL them because of file size. 

I messed up on a certain other OS's game, though.  I downloaded a 400MB file 
across 56k - 22 hours in all - only to find out that my video card (on the 
laptop, mind you - not upgradable) wasn't good enough to play the game :-(

So from that, I learned ;-)

As for where I found the INSTALL, I don't recall the URL, but webcvs.kde.org 
is probably right.  I remember having to go through the CVS link to get to 
it, CVS Browser I think it was labelled...  Mind you, I think I hit about 90% 
of the pages on your server today :-P but that's cool B')

> ]Thank you for letting us know that the Handbook list of requirements is
> ]incomplete, though.  I'll update that right away.

Don't rush on my account ;-)   Just my 2 cents worth, I'd have a 
"dependencies" link in plain view, probably on the download page, but that's 
me.  A more seasoned individual would probably already know where to look to 
find them ;-)

> ]> Just a note, has anyone noticed any issues that I should concern myself
> ]> with in connecting this to an LX200-compatible ETX-90ec?

> ]None that I know of.  Please do let us know of your experiences using the
> ]telescope control stuff.  It's brand-new code and we have as yet gotten no
> ]user feedback about it.
> ]
> ]Clear skies,
> ]Jason

Not a problem.  In fact, I'm just about to do that.  Of course, since it's 
still daylight and I'm indoors, I can't speak for the accuracy of aims.  I 
can tell you that the #497 (or is mine the #495?  I keep forgetting) autostar 
that connects to the ETX-90ec isn't a flawless performer itself.  I can line 
everything up as perfectly as I can, and when I tell it to go to Jupiter, I 
always have to touch it up.  This happens even if I sync it to a nearby 
object.

I originally had purchased an ETX-70, but there were optical abnormalities 
that I didn't see the point in putting up with.  Ironically though, the 
ETX-70 was almost perfectly aimed every time I used it.  I haven't figured 
out how something twice as expensive can be half as good at aiming.  Go 
figure.  Still, the ETX-90 is the better performer optically, and I just 
/happened/ to purchase it during their little $99 eypiece offer - which I 
would not have found had I not gone on their website looking for something 
else.  So, I'm happy ;-D

Anyway, I'll test it out and let you know what little I can...

CJ

>> ------- Additional Comments From rdieter@math.unl.edu  2003-07-23 21:30 
>> ------- AFAIK, fam/libfam is an *optional* depedancy, chosen at 
>> build-time of kdelibs. 
>  
> If that's true, then why did the bug reporter's compilation of KStars fail 
> at the linker stage with "cannot find the library `/usr/lib/libfam.la'" 
> (assuming his KDE installation isn't borked)?  
 
I'll try to explain it better this time (AFAIK):  fam/libfam is an optional 
dependance, chosen at build-time of kdelibs.  If kdelibs is built will 
fam/libfam suport, the kdelibs libtool files (.la files) will contain 
references to fam/libfam.  When trying to link any program built against this 
version of kdelibs, libtool will look for and expect to find fam/libfam for 
linking purposes.  (Even though in this case the need/use of libfam in linking 
kde applications is pretty uneccessary). 

Subject: Re:  Unlisted dependency - /usr/lib/libfam.la

Hello,

On Thursday 24 July 2003 10:00 am, you wrote:
> I'll try to explain it better this time (AFAIK):  fam/libfam is an optional
> dependance, chosen at build-time of kdelibs.  If kdelibs is built will
> fam/libfam suport, the kdelibs libtool files (.la files) will contain
> references to fam/libfam.  When trying to link any program built against
> this version of kdelibs, libtool will look for and expect to find
> fam/libfam for linking purposes.  (Even though in this case the need/use of
> libfam in linking kde applications is pretty uneccessary).

Right, I understood you.  My point was, since CJ's computer expects to find 
fam/libfam when compiling KStars, that means that his kdelibs *was* 
configured and compiled using libfam.  So why doesn't he have libfam?  The 
libfam RPM should be listed as a dependency of his kdelibs RPM (or at least 
kdelibs-devel).  It sounds like maybe the Mandrake kdelibs RPM is broken in 
this regard.

Jason

He must have libfam.so.0 in his system because that dependency is automatic. 
 
However, he doesn't seem to have libfam.la nor libfam.so. The dependency 
between kdelibs-devel and libfam-devel (or whatever they are called) is not 
automatic. So, yes, it's a packaging bug. 

Not to go off-subject (and a new report isn't necessary, I don't think...) but I tried to get 
the telescope hooked up through the software and for whatever reason it kept saying it 
wasn't connected.  I went into the device manager and started the LX-200 (classic) 
service, and I also tried the LX-200 (Autostar) service as well in different attempts.  I 
would then go into the INDI panel and try to connect (I assume by verifying the proper 
/dev/ttyS port and then hitting "power on").  When I do, "the telescope is not connected 
to the serial/USB port".  The first couple of times I tried this, it gave me an error about 
being unable to update something (my apologies, I forget what it was), and shortly 
afterward, it said it updated latitude to 0.00 and again to 51.something.  The autostar's 
setup was unchanged.  
 
I verified that the cable is good, but since I've never used the serial port on this 
machine, I can't verify that it is good.  It does show up in /dev as /dev/ttys0, a symlink 
(hardlink?  what's the diff?) to /dev/tts/0, which does exist alongside /dev/ttyS1 
(/dev/tts/1), which is my modem.  So, I have a positive on the port, just not a positive on 
the functionality of said port. 
 
I haven't put the program on my laptop yet, but I know the laptop's port works.  
Unfortunately, my schedule today involves spending the entire afternoon painting a 
house, so I doubt I'll get a chance to compile the software on the laptop to test the 
scope connex ability.  However, for when I do, could you tell me if I'm using the feature 
correctly to connect?  (i.e., how did you get yours to connect for the "this is the 
connected scope" screenshot on the website?  What scope was it?) 
 
Thanks, 
 
CJ 

kstars@30doradus.org wrote: 
 
> Right, I understood you.  My point was, since CJ's computer expects to 
> find fam/libfam when compiling KStars, that means that his kdelibs was 
> configured and compiled using libfam.  So why doesn't he have libfam?  
 
FYI, libfam != libfam-devel(contains libfam.la) 
(-: 

Hokey chokie, pokie...  I said I'd try it out on the laptop.  Thankfully, this compiled in only 
half an hour (Pentium-III 900/256MB RAM, otherwise practically identical setup to the 
desktop machine). 
 
I got the program running very quickly - I wound up having to copy the contents of 
~/kdeedu/kstars/kstars/data/* to ~/.kde/share/apps/kstars/data/*, IIRC, and I remember 
seeing something similar to this effect on the website.  Unfortunately, I tried several 
directories first (probably my lack of experience which is responsible for not knowing 
which one to try first). 
 
Anyway, once it loaded, it was up about as fast as Konqueror!  First thing I tried was to 
start the service for the LX-200 (Autostar), and then I went to the INDI panel and hit 
"Power On".  My scope is already on, and waiting at the "Align:" prompt (do I need to 
align it /first/?  I vaguely recall an issue with this in Win32/Starry Night). 
 
This is what it fed to me: 
 
2003-07-25T03:07:57 Telescope is online. Retrieving basic data... 
2003-07-25T03:07:58 Date changed, updating planetary data... 
2003-07-25T03:07:58 Site longitude updated to 0:0:0 
2003-07-25T03:07:59 Site latitude updated to 51:28:0 
 
looks like the same stuff it fed me last time...  In fact, isn't that Greenwich's location?  
Regardless, on the desktop, I had already typed in my coords.   I check my autostar...... 
 
I'll be damned.  It thinks "HALLER AIRPARK" is at 51:28 north by 0 west.  I do think it's 
working.  Sure enough, the INDI panel (once I scroll down in my limited 1024x768 
screen (man, never thought I'd say THAT was limited)) says I'm at HALLER, just like my 
autostar.  They're clearly talkin' to one another. 
 
I try setting my latlong back manually in INDI, and it swaps it, but then sets it to 
Greenwich immediately after...  bug?  view as you like...  I'll set that outside of indi and 
see what it does then... 
 
Oh, INDI tells me that my coords are invalid on longitude set.  I see "+E", so, I tried "-81" 
for 81 degrees west...  it didn't like that.  It took (180+81=261) 261 degrees east, but 
calls it "98:18 West" in autostar...   odd....  So I try the obvious:  81W and it put it into the 
autostar as 81 E.  I also tried putting a "-" /after/ the numbers, before the numbers, I tried 
putting "W" before and after, the word "WEST"...  nothing seemed to work. 
 
At this point, the intuitiveness falls to "RTFM" stage.  I would, but on the desktop, when I 
tried using the handbook, it opened generic KDE help.  BTW, the handbook /is/ 
compiled on the desktop machine, so I don't know what the deal is.  FWIW, it happens 
with a /lot/ of KDE programs on /both/ machines that only the generic KDE help will 
open, so I suspect a KDE bug and not a kstars bug.  Or a borked-install-bug. 
 
Anyway, for want of time (23:34 local) I just manually set it back to "west" on the 
handbox. 
 
I go ahead and reset the scope, and go through a quick "easy" setup just to see how 
close the AS is to INDI.   
 
Well, INDI seems to know that the scope is "pointed at regulus" (scope's OBJECT > 
IDENTIFY confirms), but it won't slew to Jupiter.  It just pauses for a moment, like it's 
slewing to the object it's pointed at.  I notice Regulus is still selected on the screen, so I 
select Jupiter and say "Center and Track".  I try slew again, same thing.  So I notice 
"slew" is still checked.  I check "idle" then "slew" again, same thing.  So, it doesn't want 
to go to Jupiter...  which, now that I think about it, should have set by now anyway. 
 
Bug?  View as you like. 
 
Wait, what is the sun doing in the middle of the sky at nearly midnight?  I double check 
my coordinates, yes, they're still where I really am, and the map shows my real location, 
so I can only assume that .......   Wait, Local Time 7 in the evening?  no...  let's try again...  
I set the right time in the software, and it now says regulus is below the horizon.  I 
double-check the scope's time, it is correct:  now 23:48 local.  It still thinks it's pointed at 
regulus.  I go to ALIGN the scope again, it finds Vega and Regulus for targets.  Dunno 
'bout Vega, but regulus is apparently below the horizon.  Something doesn't jive here, 
and I can barely keep my eyes open.  I'll check it out in the morning - after my dad 
wakes up (works nights). 
 
So, what I've found out so far is that the scope and the computer are talking under 
Linux, kstars, and INDI.  If you see an error in my methods, PLEASE tell me so I can get 
this right...  it's too late for me to think right now, anyway, so it's possible that could have 
contributed to some of the problems I had.  I just wanted to get as much of this done as 
I could as soon as possible. 
 
Sorry for the long notes...  Oh, I was thinking of a wishlist earlier...  I'll have to write 
down my ideas so I can remember them ;-) 
 
Later 
 
CJ 
 

*** Bug 62204 has been marked as a duplicate of this bug. ***