[Xastir] Re: Xastir Digest, Vol 16, Issue 6

[txniteowl]

I find Xastir v1.7.0 to be very stable on Mepis v6.0, Kubantu, U bantu, 
and not 64-bit OS.
You need to address "Festival" as to not enough explanation to make it 
work if IT really does.
So tell me. How do you get it to work? Get your act together. Clean it 
up. Your getting better since 70's, 80's, and 90's. Now it's time!

An Ole Hand.



xastir-request at xastir.org wrote:
> Send Xastir mailing list submissions to
> 	xastir at xastir.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> or, via email, send a message with subject or body 'help' to
> 	xastir-request at xastir.org
>
> You can reach the person managing the list at
> 	xastir-owner at xastir.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xastir digest..."
>
>
> Today's Topics:
>
>    1. Re: compressed objects not displayed? (Curt, WE7U)
>    2. Re: Ubuntu 6.10 Bootstrap error (Tom Russo)
>    3. Re: Ubuntu 6.10 Bootstrap error (John Ronan)
>    4. Re: Ubuntu 6.06 Boostrap (Darryl Gibson)
>    5. Re: Ubuntu 6.06 Boostrap (Darryl Gibson)
>    6. Re: Ubuntu 6.06 Boostrap (Stephen Brown Jr)
>    7. Re: Ubuntu 6.06 Boostrap (Darryl Gibson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 3 Nov 2006 12:30:50 -0800 (PST)
> From: "Curt, WE7U" <archer at eskimo.com>
> Subject: Re: [Xastir] compressed objects not displayed?
> To: Tapio Sokura <oh2kku at iki.fi>
> Cc: xastir at xastir.org
> Message-ID: <Pine.SUN.4.58.0611031228470.2467 at eskimo.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Fri, 27 Oct 2006, Tapio Sokura wrote:
>
>   
>> I've attached a simple one-minute diff against the current CVS that
>> fixes it for me,
>>     
>
> Committing it to CVS.  Thanks!
>
> --
> 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!"
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 3 Nov 2006 13:10:08 -0700
> From: Tom Russo <russo at bogodyn.org>
> Subject: Re: [Xastir] Ubuntu 6.10 Bootstrap error
> To: John Ronan <jronan at tssg.org>
> Cc: "xastir-xastir.org List" <xastir at xastir.org>
> Message-ID: <20061103201008.GA976 at bogodyn.org>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, Nov 01, 2006 at 10:28:10PM +0000, we recorded a bogon-computron collision of the <jronan at tssg.org> flavor, containing:
>   
>> Now.. to make things easy for myself I edited
>> get-maptools.sh
>>
>> ALL="   http://dl.maptools.org/dl/shapelib/shapelib-1.2.10.tar.gz\
>>         http://dl.maptools.org/dl/gdal/gdal-1.3.1.tar.gz\
>>         http://dl.maptools.org/dl/geotiff/libgeotiff/ 
>> libgeotiff-1.2.3.tar.gz"
>>
>> as pcre and proj are installed (and being recognised by xastir's ./ 
>> configure)
>>
>> shapelib was fine.
>>
>> First problem, gdal wouldn't compile
>>
>> g++ -Wall -O2 -I../../port -I../../gcore -I../../alg -I../../ogr - 
>> I../../ogr/ogrsf_frmts -I../../port -c fitdataset.cpp  -fPIC -DPIC - 
>> o ../o/.libs/fitdataset.o
>> fitdataset.cpp:177: error: extra qualification 'FITRasterBand::' on  
>> member 'FITRasterBand'
>> fitdataset.cpp: In static member function 'static GDALDataset*  
>> FITDataset::Open(GDALOpenInfo*)':
>> fitdataset.cpp:1019: warning: dereferencing type-punned pointer will  
>> break strict-aliasing rules
>> make[2]: *** [../o/fitdataset.o] Error 1
>> make[2]: Leaving directory `/home/j0n/sources/xastir/tmp/gdal-1.3.1/ 
>> frmts/fit'
>> make[1]: *** [fit-install-obj] Error 2
>> make[1]: Leaving directory `/home/j0n/sources/xastir/tmp/gdal-1.3.1/ 
>> frmts'
>> make: *** [frmts-target] Error 2
>>
>> So, I downloaded 1.3.2 by hand and tried it instead, that worked
>>     
>
> GCC 4.x is much more strict about C++, and a lot of dicey/deprecated/lazy things
> that slipped through older compilers don't get by gcc 4.x.  Some of the 
> things that are deprecated (e.g. "deprecate conversion of string constant to 
> char *", which is all over lots of codes) just spew warning upon warning, but 
> others, such as overqualifying a name:
>     class foo {
>        public:
>          double foo::bar();
>     }
> that used to be silently ignored in older gcc versions (3.x and earlier) now 
> cause compilation failures.  
>
> The particular error you mention was fixed in GDAL in February, but that's
> after 1.3.1 was released.
>
> get-maptools.sh should probably be updated to snag a later version, or folks
> with bleeding edge GNU compilers will have to do more things manually.
>
>