Re: [Xastir] Maps

2007-06-29 Thread Curt Mills
On Mon, 25 Jun 2007, Jason Winningham wrote:

> Just wondering if there would be a performance hit going from 8 bit to 24 bit
> images if someone were to implement support for 24 bit geotiffs?

There might be a small hit, but by that point there's been a lot of
math done already, so I doubt it would affect the load speed all
that much.  Only one way to really know though, implement it and
then compare.

-- 
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora

2007-06-29 Thread Jeremy Utley

On 6/29/07, Richard Polivka, N6NKO <[EMAIL PROTECTED]> wrote:


I will send the -v from gcc and the output from both runs under a
separate email. I don't think that there is a problem with xastir. I am
beginning to believe that there is an issue between the -l and the -L
calls in gcc.


Those 2 flags do completely different things:

-L - specifies directories to be searched for library files
-l - specifies libraries to be linked in, without the "lib" in the name

So, -Lrtree -lrtree flags will attempt to link in the librtree.{so,a}
file, and include the directory "rtree" in the search path used to
find libraries.  Since xastir includes the functionality of rtree in
the main executable, it's probably looking for librtree.a to compile
in static (am I right Curt?), and it will probably be inside the
directory "rtree" included with the xasitr source code.

The order of these two flags do not matter at all, since they indicate
completely different things.

Jeremy
NW7JU
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


[Xastir] CVS compile - success!!!!

2007-06-29 Thread Richard Polivka
[EMAIL PROTECTED] xastir]$ ./bootstrap.sh
6) Removing autom4te.cache directory...
5) Running aclocal...
4) Running autoheader...
3) Running autoconf...
2) Running automake...
configure.ac:36: installing `./config.sub'
configure.ac:19: installing `./missing'
configure.ac:19: installing `./install-sh'
configure.ac:36: installing `./config.guess'
callpass/Makefile.am: installing `./depcomp'
1) Checking for 'mkinstalldirs'... Not Found
   Attempting to copy it from system directories'
   Checking for 'mkinstalldirs'... Found!
Bootstrap complete.
[EMAIL PROTECTED] xastir]$ ./configure; make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes

Configuring xastir 1.9.1

checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gawk... (cached) gawk
checking for ranlib... ranlib
checking for devices... found /dev/ttyS0 and /dev/ttyS1
checking for search paths... done
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for cc_r... gcc
checking whether compiler accepts -Wno-unused-parameter... yes
checking for compiler flags... using -g -O2 -pipe -W -Wall -Wpointer-arith 
-Wstrict-prototypes -Wno-unused-parameter -pthread
checking for system... Linux
checking for gm... /usr/bin/gm
checking for /usr/bin/gm.exe... no
checking for lpr... /usr/bin/lpr
checking for gv... no
checking for festival... /usr/bin/festival
checking for gpsman... no
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for library containing tan... -lm
checking for XextAddDisplay in -lXext... yes
checking for XpGetDocumentData in -lXp... yes
checking for XtDisplay in -lXt... yes
checking for XmTextFindString in -lXm... yes
checking for curl_global_init in -lcurl... yes
checking for wget... /usr/bin/wget
checking for main in -lcompat... no
checking for sched_yield in -lrt... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for Motif headers... in default path
checking for Motif libraries... in default path
checking for working alloca.h... yes
checking for alloca... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h 

[Xastir] gcc -v

2007-06-29 Thread Richard Polivka
[EMAIL PROTECTED] xastir-1.9.1]$ gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --enable-shared --enable-threads=posix 
--enable-checking=release --with-system-zlib --enable-__cxa_atexit 
--disable-libunwind-exceptions 
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk 
--disable-dssi --enable-plugin 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre 
--enable-libgcj-multifile --enable-java-maintainer-mode 
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-cpu=generic 
--host=i386-redhat-linux
Thread model: posix
gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)
[EMAIL PROTECTED] xastir-1.9.1]$ 
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


[Xastir] v 1.9.1 compile run with -lrtree -Lrtree

2007-06-29 Thread Richard Polivka
[EMAIL PROTECTED] ~]$ cd xastir/xastir-1.9.1
[EMAIL PROTECTED] xastir-1.9.1]$ ./configure; make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes

Configuring xastir 1.9.1

checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gawk... (cached) gawk
checking for ranlib... ranlib
checking for devices... found /dev/ttyS0 and /dev/ttyS1
checking for search paths... done
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for cc_r... gcc
checking whether compiler accepts -Wno-unused-parameter... yes
checking for compiler flags... using -g -O2 -pipe -W -Wall -Wpointer-arith 
-Wstrict-prototypes -Wno-unused-parameter -pthread
checking for system... Linux
checking for gm... /usr/bin/gm
checking for /usr/bin/gm.exe... no
checking for lpr... /usr/bin/lpr
checking for gv... no
checking for festival... /usr/bin/festival
checking for gpsman... no
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for library containing tan... -lm
checking for XextAddDisplay in -lXext... yes
checking for XpGetDocumentData in -lXp... yes
checking for XtDisplay in -lXt... yes
checking for XmTextFindString in -lXm... yes
checking for curl_global_init in -lcurl... yes
checking for wget... /usr/bin/wget
checking for main in -lcompat... no
checking for sched_yield in -lrt... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for Motif headers... in default path
checking for Motif libraries... in default path
checking for working alloca.h... yes
checking for alloca... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/file.h usability... y

[Xastir] v 1.9.1 compile run with just -Lrtree

2007-06-29 Thread Richard Polivka
[EMAIL PROTECTED] ~]$ cd xastir/xastir-1.9.1
[EMAIL PROTECTED] xastir-1.9.1]$ ./configure; make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes

Configuring xastir 1.9.1

checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gawk... (cached) gawk
checking for ranlib... ranlib
checking for devices... found /dev/ttyS0 and /dev/ttyS1
checking for search paths... done
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for cc_r... gcc
checking whether compiler accepts -Wno-unused-parameter... yes
checking for compiler flags... using -g -O2 -pipe -W -Wall -Wpointer-arith 
-Wstrict-prototypes -Wno-unused-parameter -pthread
checking for system... Linux
checking for gm... /usr/bin/gm
checking for /usr/bin/gm.exe... no
checking for lpr... /usr/bin/lpr
checking for gv... no
checking for festival... /usr/bin/festival
checking for gpsman... no
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for library containing tan... -lm
checking for XextAddDisplay in -lXext... yes
checking for XpGetDocumentData in -lXp... yes
checking for XtDisplay in -lXt... yes
checking for XmTextFindString in -lXm... yes
checking for curl_global_init in -lcurl... yes
checking for wget... /usr/bin/wget
checking for main in -lcompat... no
checking for sched_yield in -lrt... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for Motif headers... in default path
checking for Motif libraries... in default path
checking for working alloca.h... yes
checking for alloca... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/file.h usability... y

Re: [Xastir] CoverSplit symbol issue with rtree in Fedora

2007-06-29 Thread Richard Polivka, N6NKO

Gents,

There is no need to start a religious war over editing ./configure. I am 
trying to understand what is going on.


I want to try a couple of items first before the CVS release.

It appears that using either "-lrtree -Lrtree" or "-Lrtree -lrtree" does 
not make a difference, It still faults out.


I will send the -v from gcc and the output from both runs under a 
separate email. I don't think that there is a problem with xastir. I am 
beginning to believe that there is an issue between the -l and the -L 
calls in gcc.


73 from 807,

Richard, N6NKO


Curt, WE7U wrote:

On Fri, 29 Jun 2007, Tom Russo wrote:

  

One could always try changing the name "CoverSplit" throughout the split_l.*
files to something else (like l_CoverSplit).  There was a brief period where
I had been confused and was suggesting to folks that they try changing
CoverSplit in a different pair of files, but that pair of files turned out not
to be used or even compiled in Xastir's use of rtree (we use only part of
it).



I just tweaked that and committed the changes to CVS.

Richard:  Please update to the latest CVS and give it a shot.  If it
fixes your problem we can leave the code as-is, else I might back
out the change.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

  

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread Ray Wells

William McKeehan wrote:


It looks like ImageMagick is not available for Debian (via apt-get anyway)
unless I'm overlooking it somewhere - if so, someone point me to the package
that I need to get.

I'll try building ImageMagick from source and see how that works.

Thanks for the suggestion.
 

I run Debian v4.0 on the main bbs system here and imagemagick is 
available via apt-get. I also checked my Kubuntu (7.04) test machine and 
imagemagick is also available there via apt-get.


All I did was apt-get install imagemagick

Ray vk2tv
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Tom Russo wrote:

> One could always try changing the name "CoverSplit" throughout the split_l.*
> files to something else (like l_CoverSplit).  There was a brief period where
> I had been confused and was suggesting to folks that they try changing
> CoverSplit in a different pair of files, but that pair of files turned out not
> to be used or even compiled in Xastir's use of rtree (we use only part of
> it).

I just tweaked that and committed the changes to CVS.

Richard:  Please update to the latest CVS and give it a shot.  If it
fixes your problem we can leave the code as-is, else I might back
out the change.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 10:55:11AM -0700, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Fri, 29 Jun 2007, Curt, WE7U wrote:
> 
> > It may be hard to find, as in a string inside a compiled library.
> 
> A google search for "CoverSplit -xastir library" found something in
> GRASS and of course R-Tree.  Perhaps there's a library that GRASS
> uses that we also may use which has R-Tree in it?

Yep.  The rtree library.  We use exactly the same rtree library that GRASS
does.  GRASS is where I got the idea.

> Then again, if it only happens on Fedora then it's likely from
> somewhere else, otherwise more of us would be seeing the problem.

One could always try changing the name "CoverSplit" throughout the split_l.*
files to something else (like l_CoverSplit).  There was a brief period where
I had been confused and was suggesting to folks that they try changing
CoverSplit in a different pair of files, but that pair of files turned out not
to be used or even compiled in Xastir's use of rtree (we use only part of
it).

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 12:33:13PM -0500, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
>  Tom,
> 
>  All I did was remove the one library search, not both. If the library was 
>  not available, linking should have failed due to an undefined reference 
>  call.

You should *never* need to edit configure.  Ever.  It is the wrong approach.
Configure is generated from configure.ac by autoconf.

>  What I will do is compile 1.9.0 straight and capture the whole process and a 
>  capture of the edited config file compile. I willl then post to the group 
>  for chewing.

Do not edit configure.  If you want to disable rtree, use "--without-rtree"
when running configure.

>  Tom Russo wrote:
> > On Fri, Jun 29, 2007 at 08:40:09AM -0500, we recorded a bogon-computron 
> > collision of the <[EMAIL PROTECTED]> flavor, containing:
> >   
> >>  I need this confirmed.
> >>
> >>  I did a Fedora 7 install on BigBox. Brought in the requisite routines to  
> >> work with 1.9.1.
> >>
> >>  configure / make / crash on CoverSplit issue.
> >>
> >>  Found "-Lrtree -lrtree" in command line that cause the crash.
> >>
> >>  Edited out "-lrtree" in configure file.
> >> 
> >
> > You should never need to edit the configure file.  You can disable rtree
> > with the "--without-rtree".  Editing out the link should cause problems,
> > because WITH_RTREE would still be defined.
> >
> > I still don't understand the reported link failure when rtree is enabled
> > on this (and only this) system.
> >
> >   
>  ___
>  Xastir mailing list
>  Xastir@xastir.org
>  http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Curt, WE7U wrote:

> It may be hard to find, as in a string inside a compiled library.

A google search for "CoverSplit -xastir library" found something in
GRASS and of course R-Tree.  Perhaps there's a library that GRASS
uses that we also may use which has R-Tree in it?

Then again, if it only happens on Fedora then it's likely from
somewhere else, otherwise more of us would be seeing the problem.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Richard Polivka, N6NKO wrote:

> It may have been covered but with no conclusion. I have to take a bunch
> of tree trimmings to the dump, so while I am doing that, I will have
> BigBox do an exhaustive search to see if there are multiple instances of
> "CoverSplit".

It may be hard to find, as in a string inside a compiled library.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Richard Polivka, N6NKO

Curt,

It may have been covered but with no conclusion. I have to take a bunch 
of tree trimmings to the dump, so while I am doing that, I will have 
BigBox do an exhaustive search to see if there are multiple instances of 
"CoverSplit".


73 from 807,
Richard, N6NKO


Curt, WE7U wrote:

On Fri, 29 Jun 2007, Richard Polivka, N6NKO wrote:

  

All I did was remove the one library search, not both. If the library
was not available, linking should have failed due to an undefined
reference call.



And the library should be available, 'cuz it's part of Xastir.

A possibility is that there's another symbol with the same name
available in another library that is on the link line, something
that we don't have any control over.  Have we discussed this before?

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

  

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Richard Polivka, N6NKO wrote:

> All I did was remove the one library search, not both. If the library
> was not available, linking should have failed due to an undefined
> reference call.

And the library should be available, 'cuz it's part of Xastir.

A possibility is that there's another symbol with the same name
available in another library that is on the link line, something
that we don't have any control over.  Have we discussed this before?

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Richard Polivka, N6NKO

Tom,

All I did was remove the one library search, not both. If the library 
was not available, linking should have failed due to an undefined 
reference call.


The executable does run on my system as I have compiled it.

What I will do is compile 1.9.0 straight and capture the whole process 
and a capture of the edited config file compile. I willl then post to 
the group for chewing.


73 from 807 and answering lunch bell,

Richard, N6NKO


Tom Russo wrote:

On Fri, Jun 29, 2007 at 08:40:09AM -0500, we recorded a bogon-computron collision of 
the <[EMAIL PROTECTED]> flavor, containing:
  

 I need this confirmed.

 I did a Fedora 7 install on BigBox. Brought in the requisite routines to 
 work with 1.9.1.


 configure / make / crash on CoverSplit issue.

 Found "-Lrtree -lrtree" in command line that cause the crash.

 Edited out "-lrtree" in configure file.



You should never need to edit the configure file.  You can disable rtree
with the "--without-rtree".  Editing out the link should cause problems,
because WITH_RTREE would still be defined.

I still don't understand the reported link failure when rtree is enabled
on this (and only this) system.

  

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Tom Russo wrote:

> There's
> probably a different way to go about it so that we don't have bugs to work
> around.

Yes.  Destroy the dialog and build it from scratch, then display the
new one.  Ugly.


> Then again, maybe we should get started on Xastir 2 so we don't use Motif
> at all ...

Great minds think alike.  Well, maybe a greater and a lesser mind
can think alike too?

One could perhaps compute which is which from the degrees we hold,
but perhaps we should just let people wonder.  hi hi

If we start on non-Motif, then we have to argue on which widget set.
Or if we do it _very_ right, separating the GUI code from everything
nicely, we could do Qt _and_ Gtk+, perhaps even adding in WxWidgets
as well.

The distributed approach to Xastir2 allows us to break up the app
into multiple pieces, any of which could be any widget set.  Or any
language.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 08:49:21AM -0700, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Fri, 29 Jun 2007, Tom Russo wrote:
> 
> > On another note, Fedora is completely dropping OpenMotif because its license
> > is considered incompatible with Fedora's, so Fedora users will
> > no longer have access so some of the dialog box tricks that Xastir plays.
> 
> Just to be clear, it's not a trick.  Standard Motif programming
> techniques.  You're allowed to change a dialog that's currently
> displayed and it is supposed to recompute all the widget geometries
> and redisplay the appropriate thing.  Motif does it properly,
> Lesstif does not.

Nod.

But apparently enough applications work Just Fine with LessTif that it is
seen as a completely viable replacement.  So most applications must not
do the changing of a dialog in the same way that Xastir does.  *shrug*
At the moment, Xastir is set up so that lesstif users get a less snazzy
view of Xastir than OpenMotif users do, just to work around this bug.  There's
probably a different way to go about it so that we don't have bugs to work
around.  

Then again, maybe we should get started on Xastir 2 so we don't use Motif
at all ...

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Curt, WE7U wrote:

> On Fri, 29 Jun 2007, Tom Russo wrote:
>
> > On another note, Fedora is completely dropping OpenMotif because its license
> > is considered incompatible with Fedora's, so Fedora users will
> > no longer have access so some of the dialog box tricks that Xastir plays.
>
> Just to be clear, it's not a trick.  Standard Motif programming
> techniques.  You're allowed to change a dialog that's currently
> displayed and it is supposed to recompute all the widget geometries
> and redisplay the appropriate thing.  Motif does it properly,
> Lesstif does not.

BTW:  I'm pissed off at Lesstif in this case, not Tom.  I really
appreciate all he does (in his limited time) for the project.

Then again, I'm really not pissed off at Lesstif either:  They're
doing a clean-room rewrite of Motif, which is a lot of code, and
they don't have _all_ of the features of Motif yet.  What they do
have of course has some bugs in it.  They haven't had as many years
to work on it as Motif, and certainly not the funding or the
programmers thrown at it that Motif did.

So we work with what we have.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Tom Russo wrote:

> On another note, Fedora is completely dropping OpenMotif because its license
> is considered incompatible with Fedora's, so Fedora users will
> no longer have access so some of the dialog box tricks that Xastir plays.

Just to be clear, it's not a trick.  Standard Motif programming
techniques.  You're allowed to change a dialog that's currently
displayed and it is supposed to recompute all the widget geometries
and redisplay the appropriate thing.  Motif does it properly,
Lesstif does not.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 08:15:18AM -0700, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Fri, 29 Jun 2007, Tom Russo wrote:
> 
> > You should never need to edit the configure file.  You can disable rtree
> > with the "--without-rtree".  Editing out the link should cause problems,
> > because WITH_RTREE would still be defined.
> >
> > I still don't understand the reported link failure when rtree is enabled
> > on this (and only this) system.
> 
> We need the exact error message.  Maybe we have that in an earlier
> e-mail though.

It was in several older emails in the last month or so.

It's:

> /usr/bin/ld: rtree/librtree.a(split_l.o)(.text+0x27f): unresolvable R_386_32 r
elocation against symbol `CoverSplit'
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: ld returned 1 exit status

So far the only folks who have reported this are those who are running Fedora 7,
and not all of them, either.

I have not had time to build a VMware virtual machine with Fedora in it, even
though I've downloaded the install DVD.  Once I get a chance I'll try to 
follow the F7 directions on the wiki to see if I can reproduce the failure
and track it down.  None of my systems get this error during link.

It doesn't seem to be a compiler version issue, either, as the gcc version 
reporded by the original reporter was gcc 4.1.1. (Barrie McConnell, back in
April).  And looking back over emails that was on FC6, not F7.  I know
that several people here have built on FC6, so there is something very 
fishy going on, as this is not universal.

On another note, Fedora is completely dropping OpenMotif because its license
is considered incompatible with Fedora's, so Fedora users will 
no longer have access so some of the dialog box tricks that Xastir plays.


-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Only seeing posits of path APZ256 | 7

2007-06-29 Thread Curt, WE7U
On Thu, 28 Jun 2007, Rick Bolen (HM) wrote:

> Thanks. I edited the tnc-startup.ts2k from an xterm and then stop\start the
> interface from within Xastir to get changes picked up.
>
> After fiddling, turning "MCOM OFF" seemed to improve things significantly.
> I'm taking a road trip shortly, so i'll test and mess with this config for
> awhile. If I get a TS-2000 config that works reliably I'll share the tnc
> configs.
>
>  Thanks for the pointers...

Capture some of the output of the TNC with a dumb-terminal program
and I'll take a look at it to see if I can help diagnose the
problem.  Keep it down to a few 10's or maybe low 100's of kbytes
though please, and send it to my address directly instead of the
list.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 09:07:25AM -0600, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Fri, Jun 29, 2007 at 08:40:09AM -0500, we recorded a bogon-computron 
> collision of the <[EMAIL PROTECTED]> flavor, containing:
> >  I need this confirmed.
> > 
> >  I did a Fedora 7 install on BigBox. Brought in the requisite routines to 
> >  work with 1.9.1.
> > 
> >  configure / make / crash on CoverSplit issue.
> > 
> >  Found "-Lrtree -lrtree" in command line that cause the crash.
> > 
> >  Edited out "-lrtree" in configure file.
> 
> You should never need to edit the configure file.  You can disable rtree
> with the "--without-rtree".  Editing out the link should cause problems,
> because WITH_RTREE would still be defined.
> 
> I still don't understand the reported link failure when rtree is enabled
> on this (and only this) system.

Ok, I just reread your post.  The presence of -lrtree in the configure file
is not the bug, as that is needed when rtree is enabled.  The bug is obscure
and is platform specific.  Your approach is just to try to disable rtree by
editing configure, but that is not the correct approach --- to get xastir to 
compile on F7 until we figure out why the link is failing should just require 
that you configure with "--without-rtree", and someday one hopes there some 
extra hours when someone can figure out what the obscure link error actually 
means so that this work-around isn't necessary.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Curt, WE7U
On Fri, 29 Jun 2007, Tom Russo wrote:

> You should never need to edit the configure file.  You can disable rtree
> with the "--without-rtree".  Editing out the link should cause problems,
> because WITH_RTREE would still be defined.
>
> I still don't understand the reported link failure when rtree is enabled
> on this (and only this) system.

We need the exact error message.  Maybe we have that in an earlier
e-mail though.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Tom Russo
On Fri, Jun 29, 2007 at 08:40:09AM -0500, we recorded a bogon-computron 
collision of the <[EMAIL PROTECTED]> flavor, containing:
>  I need this confirmed.
> 
>  I did a Fedora 7 install on BigBox. Brought in the requisite routines to 
>  work with 1.9.1.
> 
>  configure / make / crash on CoverSplit issue.
> 
>  Found "-Lrtree -lrtree" in command line that cause the crash.
> 
>  Edited out "-lrtree" in configure file.

You should never need to edit the configure file.  You can disable rtree
with the "--without-rtree".  Editing out the link should cause problems,
because WITH_RTREE would still be defined.

I still don't understand the reported link failure when rtree is enabled
on this (and only this) system.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread William McKeehan
Well, that did the trick. The map is displaying fine now.

Thanks!
-- 
William McKeehan
KI4HDU

On Fri, June 29, 2007 9:44 am, Lance Cotton wrote:
> William McKeehan wrote:
>> It looks like ImageMagick is not available for Debian (via apt-get anyway)
>> unless I'm overlooking it somewhere - if so, someone point me to the package
>> that I need to get.
>>
>> I'll try building ImageMagick from source and see how that works.
>>
>> Thanks for the suggestion.
>
> Look for libmagick9 and libmagick9-dev. I'm not certain on that, but I
> run Ubuntu, a debian-based distro.
>
> I do recall that it's not called "ImageMagick" in the repository.
>
> -Lance
>

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Map formats

2007-06-29 Thread Curt, WE7U
On Thu, 28 Jun 2007, Earl Needham via Kubuntu wrote:

>   I have Precision Mapping available, I use it with UI-View32.  Is there 
> a way
> to use PM with Xastir?

Only by taking snapshots of the maps you want, creating a
PNG/JPG/GIF/what-have-you raster image out of each one, creating a
.geo file to go with each one, then letting Xastir have at 'em.

We don't support _any_ commercial mapping programs for several good
reasons.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread Lance Cotton

William McKeehan wrote:

It looks like ImageMagick is not available for Debian (via apt-get anyway)
unless I'm overlooking it somewhere - if so, someone point me to the package
that I need to get.

I'll try building ImageMagick from source and see how that works.

Thanks for the suggestion.


Look for libmagick9 and libmagick9-dev. I'm not certain on that, but I 
run Ubuntu, a debian-based distro.


I do recall that it's not called "ImageMagick" in the repository.

-Lance
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


[Xastir] CoverSplit symbol issue with rtree in Fedora 7 ... may have found the bug

2007-06-29 Thread Richard Polivka, N6NKO

I need this confirmed.

I did a Fedora 7 install on BigBox. Brought in the requisite routines to 
work with 1.9.1.


configure / make / crash on CoverSplit issue.

Found "-Lrtree -lrtree" in command line that cause the crash.

Edited out "-lrtree" in configure file.

Make clean / configure / make / success!!

Now to a meeting at work. Further updates to follow...

73 from 807,

Richard, N6NKO

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread William McKeehan
It looks like ImageMagick is not available for Debian (via apt-get anyway)
unless I'm overlooking it somewhere - if so, someone point me to the package
that I need to get.

I'll try building ImageMagick from source and see how that works.

Thanks for the suggestion.
-- 
William McKeehan
KI4HDU

On Fri, June 29, 2007 8:03 am, Lance Cotton wrote:
> William McKeehan wrote:
>> xdpyinfo confirms that my color depth is 16.
>>
>> Any further ideas on how to debug why I don't see the Radar image?
>
> I had to recompile with ImageMagick instead of GraphicsMagick to get it
> to work.
>
> -Lance
>
>

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread Lance Cotton

William McKeehan wrote:

xdpyinfo confirms that my color depth is 16.

Any further ideas on how to debug why I don't see the Radar image?


I had to recompile with ImageMagick instead of GraphicsMagick to get it 
to work.


-Lance

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Radar display

2007-06-29 Thread William McKeehan
Thanks!

xdpyinfo confirms that my color depth is 16.

Any further ideas on how to debug why I don't see the Radar image?
-- 
William McKeehan
KI4HDU

On Thu, June 28, 2007 10:04 pm, Tom Russo wrote:
> On Thu, Jun 28, 2007 at 08:31:07PM -0400, we recorded a bogon-computron
> collision of the <[EMAIL PROTECTED]> flavor, containing:
>>
>> > I've seen issues before where VNC, the X11 server, or the remote
>> > display machine had different colordepths, so check all three of
>> > those.
>>
>> Well, I'm not positive, but I think my X11 server is running at 16 (that's
>> set
>> as the default in xorg.conf); if there's a way to tell, please let me know.
>
> "xdpyinfo" should tell you what the default color depth is.
>
> --
> Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
> Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
> "And, isn't sanity really just a one-trick pony anyway? I mean all you get is
>  one trick, rational thinking, but when you're good and crazy, oooh, oooh,
>  oooh, the sky is the limit!"  --- The Tick
>

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Configure Error

2007-06-29 Thread Richard Polivka, N6NKO

Gents,

About OpenMotif, look at the following link: http://lwn.net/Articles/197744/

Fedora was planning, and did from what I can find, to drop OpenMotif 
because of licensing issues.


You will probably have to use LessTif, which is available via Pirut.

There was an email that I posted on what was needed to do Xastir on 
Fedora 7. I believe that applies to FC6 as well.


73 from 807,

Richard, N6NKO


Tom Russo wrote:

On Thu, Jun 28, 2007 at 05:28:44PM -0700, we recorded a bogon-computron collision of 
the <[EMAIL PROTECTED]> flavor, containing:
  

Loaded Fedora Core 6, as I gave up trying to compile under Cygwin.

When I run Configure I get an error that Motif headers are not loaded.

I thought OpenMotif 2.3 was included in FC6?



The libraries might be, but the -dev package (with the development headers
needed by Xastir) probably isn't.  You need to add that one package.

  

Is there any easy way to fix this w/o downloading OpenMotif again?



Yep.  Just add the -dev package.  I'm sorry, I don't know what it's called.
Check the Xastir wiki (www.xastir.org, click "Xastir Documentation" and
then "HowTos").  There's a page there that documents how to get Xastir running
on Fedora.

  

___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir