Re: [Xastir] Black jpg maps.
> On Sat, 5 Jul 2008, Curt, WE7U wrote: > >> On Sat, 5 Jul 2008, Mitch wrote: >> >>> Installed June 26 2008 version of XASTIR 1.9.3, it compiled OK with >>> GraphicsMagick. >>> >>> It seems it cannot handle *.jpg correctly. The X server has been set to >>> 16 >>> bit colour as suggested in the FAQ. >> >> Black images are an indication that the *Magick package wasn't >> compiled with the correct options. > > For anyone who really cares, the correct option during > GraphicsMagick configure is: > > --with-quantum-depth=16 > > If the package maintainers didn't specify that during the configure > stage it defaults to "8" which results in the black images being > rendered in Xastir. > Hiya Curt and Kurt... ;) It sure is an RPM issue, the QuantumDepth has not been set in GraphicsMagick. The latest source of GraphicsMagick allows ./configure --with-quantum-depth=16 however it has problems with Perl so nearly there. Installed the latest version of Perl, 5.10.0 via YUM UPDATE (Fedora 9). However a 'make' of GraphicsMagick complains of a missing file in the directory below called 'libperl.a' and fails. /usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE/ This file IS there: 'libperl.so' so copied it to 'libperl.a', make clean, then make again and all OK. Recompiled Xastir and all graphic functions are back to normal. ImageMagick is OK: /usr/lib/ImageMagick-6.3.8/config/configure.xml Best to 'rpm -e GraphicsMagick GraphicsMagick-devel' prior make install of the latest source which is available from GraphicsMagick.org Thanks to all and regs, Rod. > If you forget the details in the future, remember the > xastir/scripts/LSB-BUILD-GRAPHICSMAGICK script. You'll see the > above configure option plainly listed. > > ImageMagick is probably similar since GM is a fork of the IM code. > > -- > 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!" > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > Supported by melecom with a Fedora server. > > VK5KFB -- ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
Tom Russo wrote: On Sat, Jul 05, 2008 at 11:48:30AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: On Sat, 5 Jul 2008, Tom Russo wrote: It looks as if the packaged version of libgeotiff-dev on Ubuntu 8.03 puts the include files down a level under /usr/include instead of dumping them right at the top level. On my systems, where I don't use the packaged versions, they're at top level. We'll pick 'em up Just Fine if they're in /usr/include, but not if they're in /usr/include/geotiff/. This is pretty much a package maintainer issue. libgeotiff wasn't even available as an Ubuntu package for quite some time --- the wiki pages for installing libgeotiff on Ubunutu spend a fair amount of time telling the user how to do it from source, precisely because it wasn't available in the package system for at least the last few releases of Ubuntu.. For what it's worth gdal is also non-standard on Ubuntu 8. Xastir configure finds the includes but cannot link the library because there is no simple reference to it as /usr/lib/libgdal.a or /usr/lib/libgdal.so. There are only the fully qualified file names - /usr/lib/libgdal1.4.0.a and /usr/lib/libgdal1.4.0.so.1.11.4 with a symbolic link /usr/lib/libgdal1.4.0. Xastir built fine after I created the simple symbolic links libgdal.a and libgdal.so. Other people who try to compile on Ubuntu Hardy may find that info useful. Dick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
On Sat, Jul 05, 2008 at 12:02:07PM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Sat, 5 Jul 2008, Tom Russo wrote: > > > Adding configure command line options is always necessary to deal with > > nonstandard installs. Peppering the configure script with tricks to look > > everywhere that might have the desired files is unmaintainable and often > > breaks. Look at the mess we have for BDB --- it tries all manner of crazy > > things to find db headers, and often screws up, all because no two installs > > of BDB seem to be consistent. > > Rgr. BDB: Another of nemesis of ours, and of other projects! > > If the /usr/include/geotiff/ directory becomes commonplace later I'd > advocate adding it to our autoconf scripts. But at this point it isn't --- geotiff's install doesn't do that itself, the Ubuntu package maintainer must have decided to isolate the headers for some reason, and just did it. A note to the maintainer might be in order. Some packages do that, but it is not the norm. I'm not sure that many packages that use libgeotiff are going to expect its headers to be in nonstandard locations. -- 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 "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
On Sat, 5 Jul 2008, Tom Russo wrote: Adding configure command line options is always necessary to deal with nonstandard installs. Peppering the configure script with tricks to look everywhere that might have the desired files is unmaintainable and often breaks. Look at the mess we have for BDB --- it tries all manner of crazy things to find db headers, and often screws up, all because no two installs of BDB seem to be consistent. Rgr. BDB: Another of nemesis of ours, and of other projects! If the /usr/include/geotiff/ directory becomes commonplace later I'd advocate adding it to our autoconf scripts. -- 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] geotiff includes on Ubuntu 8.03
On Sat, Jul 05, 2008 at 11:48:30AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Sat, 5 Jul 2008, Tom Russo wrote: > > > The other way to do it is to specify CPPFLAGS as a configure argument rather > > than as an exported environment variable: > > > > > > ../xastir/configure CPPFLAGS="-I/usr/include/geotiff" > > I'm curious as to the reason it's having trouble finding the geotiff > includes in /usr/include. That's where mine are and I'm having no > such difficulty. I run "./configure" and it finds everything on > OpenSuSE-11.0. The 9.x and 10.x series found it just fine as well. It looks as if the packaged version of libgeotiff-dev on Ubuntu 8.03 puts the include files down a level under /usr/include instead of dumping them right at the top level. On my systems, where I don't use the packaged versions, they're at top level. We'll pick 'em up Just Fine if they're in /usr/include, but not if they're in /usr/include/geotiff/. This is pretty much a package maintainer issue. libgeotiff wasn't even available as an Ubuntu package for quite some time --- the wiki pages for installing libgeotiff on Ubunutu spend a fair amount of time telling the user how to do it from source, precisely because it wasn't available in the package system for at least the last few releases of Ubuntu.. > Is there an autoconf test that failing for some obscure reason on > their systems? Unless our probe deliberately were to search down a level if it fails to find headers on the first try (which it does not do), it wouldn't pick them up when they're installed in weird place like this. Adding configure command line options is always necessary to deal with nonstandard installs. Peppering the configure script with tricks to look everywhere that might have the desired files is unmaintainable and often breaks. Look at the mess we have for BDB --- it tries all manner of crazy things to find db headers, and often screws up, all because no two installs of BDB seem to be consistent. -- 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 "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
On Sat, 5 Jul 2008, Tom Russo wrote: The other way to do it is to specify CPPFLAGS as a configure argument rather than as an exported environment variable: ../xastir/configure CPPFLAGS="-I/usr/include/geotiff" I'm curious as to the reason it's having trouble finding the geotiff includes in /usr/include. That's where mine are and I'm having no such difficulty. I run "./configure" and it finds everything on OpenSuSE-11.0. The 9.x and 10.x series found it just fine as well. Is there an autoconf test that failing for some obscure reason on their systems? -- 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] geotiff includes on Ubuntu 8.03
On Sat, Jul 05, 2008 at 02:31:57PM -0400, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > > Thanks, Richard. Setting the environment variable worked fine for me > after it did it correctly, as Tom pointed out. The other way to do it is to specify CPPFLAGS as a configure argument rather than as an exported environment variable: ../xastir/configure CPPFLAGS="-I/usr/include/geotiff" (I never do configure in the same directory as the source, so you'll never see "./configure" in my instructions. It is cleaner to use an empty build directory instead.) Doing the configure with CPPFLAGS as one if its command line arguments this way has one advantage --- the CPPFLAGS setting will wind up appearing in the initial comments of config.log. You can then always just look in that file six months after you last configured the code just to remember everything you had to do last time. If you do it with exported environment variables, that information isn't preserved in config.log. > Richard Polivka, N6NKO wrote: > > In the case of my Fedora 8 install, I put in the line > > "-I/usr/include/libgeotiff" to get rid of the same message. > > > > 73 from 807, > > > > Richard, N6NKO > > > > > > Tom Russo wrote: > >> On Fri, Jul 04, 2008 at 11:43:20AM -0400, we recorded a > >> bogon-computron collision of the <[EMAIL PROTECTED]> flavor, > >> containing: > >> > >>> When I build xastir-1.9.3-2008-* on Ubuntu 8.03 the build fails > >>> because it > >>> cannot find the includes for geotiff. > >>> > >>> - ./configure reports that it will use geotiff > >>> > >>> - The compile fails because xtiffio.h and geo_normalize.h cannot be > >>> found > >>> > >>> - If I edit src/Makefile and insert the appropriate includes (i.e., > >>> -I) xastir > >>> builds without error. > >>> > >>> - If I try the correct procedure (as indicated ./configure help info) > >>> > >>>export CPPFLAGS=/usr/include/geotiff > >>> > >> > >> That's not the correct procedure. > >> > >> export CPPFLAGS="-I/usr/include/geotiff" is the correct thing. > >> > >> Using what you tried would force invalid arguments into the compilation > >> command line, and result in the error you see. > >> > >> > >>>./configure --without-ax25 --with-geotiff --without-festival > >>> > >>> ./configure fails very early with the error "configure: error: C > >>> compiler > >>> cannot create executables" > >>> > >>> Is there a better way to tell ./configure the location of the includes? > >>> > >>> Thanks, > >>> > >>> Dick > >>> ___ > >>> Xastir mailing list > >>> Xastir@xastir.org > >>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > >>> > >> > >> > > ___ > > Xastir mailing list > > Xastir@xastir.org > > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > > > ___ > 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 "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
Thanks, Richard. Setting the environment variable worked fine for me after it did it correctly, as Tom pointed out. Dick Richard Polivka, N6NKO wrote: In the case of my Fedora 8 install, I put in the line "-I/usr/include/libgeotiff" to get rid of the same message. 73 from 807, Richard, N6NKO Tom Russo wrote: On Fri, Jul 04, 2008 at 11:43:20AM -0400, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: When I build xastir-1.9.3-2008-* on Ubuntu 8.03 the build fails because it cannot find the includes for geotiff. - ./configure reports that it will use geotiff - The compile fails because xtiffio.h and geo_normalize.h cannot be found - If I edit src/Makefile and insert the appropriate includes (i.e., -I) xastir builds without error. - If I try the correct procedure (as indicated ./configure help info) export CPPFLAGS=/usr/include/geotiff That's not the correct procedure. export CPPFLAGS="-I/usr/include/geotiff" is the correct thing. Using what you tried would force invalid arguments into the compilation command line, and result in the error you see. ./configure --without-ax25 --with-geotiff --without-festival ./configure fails very early with the error "configure: error: C compiler cannot create executables" Is there a better way to tell ./configure the location of the includes? Thanks, Dick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] geotiff includes on Ubuntu 8.03
In the case of my Fedora 8 install, I put in the line "-I/usr/include/libgeotiff" to get rid of the same message. 73 from 807, Richard, N6NKO Tom Russo wrote: On Fri, Jul 04, 2008 at 11:43:20AM -0400, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: When I build xastir-1.9.3-2008-* on Ubuntu 8.03 the build fails because it cannot find the includes for geotiff. - ./configure reports that it will use geotiff - The compile fails because xtiffio.h and geo_normalize.h cannot be found - If I edit src/Makefile and insert the appropriate includes (i.e., -I) xastir builds without error. - If I try the correct procedure (as indicated ./configure help info) export CPPFLAGS=/usr/include/geotiff That's not the correct procedure. export CPPFLAGS="-I/usr/include/geotiff" is the correct thing. Using what you tried would force invalid arguments into the compilation command line, and result in the error you see. ./configure --without-ax25 --with-geotiff --without-festival ./configure fails very early with the error "configure: error: C compiler cannot create executables" Is there a better way to tell ./configure the location of the includes? Thanks, Dick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Black jpg maps.
On Sat, 5 Jul 2008, Curt, WE7U wrote: On Sat, 5 Jul 2008, Mitch wrote: Installed June 26 2008 version of XASTIR 1.9.3, it compiled OK with GraphicsMagick. It seems it cannot handle *.jpg correctly. The X server has been set to 16 bit colour as suggested in the FAQ. Black images are an indication that the *Magick package wasn't compiled with the correct options. For anyone who really cares, the correct option during GraphicsMagick configure is: --with-quantum-depth=16 If the package maintainers didn't specify that during the configure stage it defaults to "8" which results in the black images being rendered in Xastir. If you forget the details in the future, remember the xastir/scripts/LSB-BUILD-GRAPHICSMAGICK script. You'll see the above configure option plainly listed. ImageMagick is probably similar since GM is a fork of the IM code. -- 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] Black jpg maps.
We of the Grand Order of the Magnificent K thank you. 8-} 8-} 73/Kurt Mitch wrote: Hi to All, Phew ... FC4 ==> F9 upgrade has been successful! Installed June 26 2008 version of XASTIR 1.9.3, it compiled OK with GraphicsMagick. It seems it cannot handle *.jpg correctly. The X server has been set to 16 bit colour as suggested in the FAQ. Any clues? Fab to have the "Fetch Findu Trail" working again, great stuff. Sorry for misspelling Curt earlier too! Regards, Rod. VK5KFB -- ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir -- Kurt A. Freiberger Austin, TX [EMAIL PROTECTED] Amateur Radio Callsign WB5BBW AIM Handle: WB5BBW "Reputation is what other people know about you. Honor is what you know about yourself." - Lois McMaster Bujold - "A Civil Campaign" ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Black jpg maps.
On Sat, 5 Jul 2008, Mitch wrote: Installed June 26 2008 version of XASTIR 1.9.3, it compiled OK with GraphicsMagick. It seems it cannot handle *.jpg correctly. The X server has been set to 16 bit colour as suggested in the FAQ. Black images are an indication that the *Magick package wasn't compiled with the correct options. Try ImageMagick instead to see if that might work. Maybe the package maintainers got the correct configure options for that one. -- 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
