Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Kevin Paetzold
Curt: The fix worked and I rebuilt with no issues after the update. Thanks! 73, K1KWP Curt, WE7U wrote: On Fri, 12 Jan 2007, Curt, WE7U wrote: After this bit of code we look for the include and lib files we need. The problem is that we already did the AC_DEFINE() for HAVE_GRAPHICSMAGICK be

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, William McKeehan wrote: > I'm trying to do a cygwin build once or twice a month to make sure things > don't get too broken before someone realizes it; I don't know if any of the > developers run it or not. If so, probably not regularly. Any bit of testing on lesser-used plat

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread William McKeehan
That's what I thought, but I wanted to run it by the experts just in case. Thanks again guys for what you are doing. I'm trying to do a cygwin build once or twice a month to make sure things don't get too broken before someone realizes it; I don't know if any of the developers run it or not. --

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Tom Russo
On Fri, Jan 12, 2007 at 03:29:13PM -0500, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Well, however long it took, the important thing is that it works again! > > I do get some messages when I'm building, but it builds. > > Thanks again for all of your

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread William McKeehan
Well, however long it took, the important thing is that it works again! I do get some messages when I'm building, but it builds. Thanks again for all of your help (all of you guys)! Here's the current output from my make command. make all-recursive make[1]: Entering directory `/home/mckeehan/x

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Curt, WE7U wrote: > Give it another shot now. Should work better for you. Sorry for > the delay in figuring this one out. Sometimes it takes me longer. I meant "takes _us_ longer", as Tom was the critical link in figuring this one out. Thanks Tom. -- Curt, WE7U. APRS C

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
Give it another shot now. Should work better for you. Sorry for the delay in figuring this one out. Sometimes it takes me longer. -- 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 co

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Tom Russo wrote: > Yep. Commit to maps.c on 5 Jan 2007 introduced two instances of strcasestr > into maps.c. Clearly, strcasestr isn't in the cygwin libraries, so the build > pukes at the link phase. Perhaps a case-insensitive comparison isn't > necessary in this instance,

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Tom Russo wrote: > strcasestr must not be available on Cygwin, and the changes to the print > properties dialog must have introduced a use of it. Yep, that looks like the case. That should be an easy fix too. It's in two places. -- Curt, WE7U. APRS Client Comparisons: htt

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Tom Russo
On Fri, Jan 12, 2007 at 11:24:27AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, Jan 12, 2007 at 01:05:43PM -0500, we recorded a bogon-computron > collision of the <[EMAIL PROTECTED]> flavor, containing: > > ./configure seems to have worke

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Tom Russo
On Fri, Jan 12, 2007 at 01:05:43PM -0500, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > ./configure seems to have worked, but the build still fails. In my opinion, > this failure has to be related to some change in the Xastir source since > December 17. O

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, William McKeehan wrote: > I'll go back to some devel snapshots and see if I can figure out when it was > last working... For what it's worth, I'm compiling on SuSE Linux on my desktop and laptop with OpenMotif and the current sources, plus the LSB Binary compiles on both mach

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread William McKeehan
I started with a ./bootstrap.sh, that's become habbit for me, I do it evertime if I need it or not :-) I'll go back to some devel snapshots and see if I can figure out when it was last working... -- William McKeehan On Fri, January 12, 2007 1:12 pm, Curt, WE7U wrote: > On Fri, 12 Jan 2007, Will

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, William McKeehan wrote: > ./configure seems to have worked, but the build still fails. In my opinion, > this failure has to be related to some change in the Xastir source since > December 17. On December 17 I was able to build Xastir successfully and have > not updated my Cygw

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, William McKeehan wrote: > ./configure seems to have worked, but the build still fails. In my opinion, > this failure has to be related to some change in the Xastir source since > December 17. On December 17 I was able to build Xastir successfully and have > not updated my Cygw

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread William McKeehan
./configure seems to have worked, but the build still fails. In my opinion, this failure has to be related to some change in the Xastir source since December 17. On December 17 I was able to build Xastir successfully and have not updated my Cygwin setup since then. Here's the log from the make tha

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Curt, WE7U wrote: > After this bit of code we look for the include and lib files we > need. The problem is that we already did the AC_DEFINE() for > HAVE_GRAPHICSMAGICK before the tests. The ImageMagick section may > be similar. Fixed both sections. The fixes have made it

Re: [Xastir] cygwin compile problem me also

2007-01-12 Thread Curt, WE7U
On Thu, 11 Jan 2007, Curt, WE7U wrote: > Sure looks the same... One other user reported that the > GraphicsMagick tests did a proper fail-over now on Cygwin after the > last round of tweaks and that it then found ImageMagick and compiled > it in. Perhaps it got broken again with later simplifica

Re: [Xastir] cygwin compile problem me also

2007-01-11 Thread William McKeehan
The configure step is working fine - as expected, it's finding and configuring with ImageMagick. Beyond that, it will not build. any longer. -- William McKeehan On Thu, January 11, 2007 1:32 pm, Curt, WE7U wrote: > On Thu, 11 Jan 2007, Tom Russo wrote: > >> I'm assuming it's this one: >> >> Will

Re: [Xastir] cygwin compile problem me also

2007-01-11 Thread Curt, WE7U
On Thu, 11 Jan 2007, Tom Russo wrote: > I'm assuming it's this one: > > William wrote: > >I'm configured with ImageMagick on Cygwin, but I get the following error: > > > >gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I/usr/X11R6/include > >-I/usr/include -DXASTIR_DATA_BASE=\"/usr/local/shar

Re: [Xastir] cygwin compile problem me also

2007-01-11 Thread Tom Russo
On Thu, Jan 11, 2007 at 06:48:17AM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Thu, 11 Jan 2007, Kevin Paetzold wrote: > > > I also have the same compiler issue with maps.o that > > William McKeehan reported. > > Wah. That helps me zero. I

Re: [Xastir] cygwin compile problem me also

2007-01-11 Thread Curt, WE7U
On Thu, 11 Jan 2007, Kevin Paetzold wrote: > I also have the same compiler issue with maps.o that > William McKeehan reported. Wah. That helps me zero. I recognize his name of course, but I'm running 150-200 e-mails a day here so the turn-over on problem e-mails is pretty fast. You'll have to

[Xastir] cygwin compile problem me also

2007-01-11 Thread Kevin Paetzold
I also have the same compiler issue with maps.o that William McKeehan reported. This seemed to start with a CVS import of XASTIR that I did about 2 wks or so ago. I did not do a cygwin update between the time that I did not have this issue and the time that I started to have this issue. It seem

Re: [Xastir] cygwin compile problem again

2007-01-10 Thread Curt, WE7U
On Wed, 10 Jan 2007, William McKeehan wrote: > I changed nothing (no cygwin updates, etc.) since last successful build > December 17. Back then is when I was playing with GraphicsMagick vs > ImageMagick on Cygwin and discovered that it only worked with ImageMagick. > > Anyone else running Cygwin?

Re: [Xastir] cygwin compile problem again

2007-01-10 Thread William McKeehan
I changed nothing (no cygwin updates, etc.) since last successful build December 17. Back then is when I was playing with GraphicsMagick vs ImageMagick on Cygwin and discovered that it only worked with ImageMagick. Anyone else running Cygwin? Can you build with the latest CVS? (i.e., is it a ME is

Re: [Xastir] cygwin compile problem again

2007-01-10 Thread Curt, WE7U
On Wed, 10 Jan 2007, William McKeehan wrote: > That got me around the first error and on to another set that I really don't > understand. Here's a log from a second make command (i.e., not the full build, > just the last step that fails): Looks to me like perhaps you have some X11 stuff that does

Re: [Xastir] cygwin compile problem again

2007-01-10 Thread William McKeehan
That got me around the first error and on to another set that I really don't understand. Here's a log from a second make command (i.e., not the full build, just the last step that fails): make all-recursive make[1]: Entering directory `/home/mckeehan/xastir' Making all in src make[2]: Entering d

Re: [Xastir] cygwin compile problem again

2007-01-10 Thread Curt, WE7U
On Wed, 10 Jan 2007, William McKeehan wrote: > /usr/include/GraphicsMagick/magick/api.h:31:36: magick/magick_config.h: No > such file or directory > > This leads to a number of errors and an unsuccessful build. Looks like it > thinks it has GraphicsMagick? Yea. Try running configure with the "--

[Xastir] cygwin compile problem again

2007-01-10 Thread William McKeehan
I'm configured with ImageMagick on Cygwin, but I get the following error: gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I/usr/X11R6/include -I/usr/include -DXASTIR_DATA_BASE=\"/usr/local/share/xastir\" -g -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -Wno-unused-parameter -MT maps.o -

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Curt, WE7U wrote: > So... On to the next question: > > Does AC_CHECK_PROG(), which we use to find Magick-config, > GraphicsMagick-config, and gdal-config, also use one of the > environment variables for its path? If so our code there can be > made simpler via the same method.

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Tom Russo wrote: > What with systems like LSB stuffing things in /opt that we might not actually > want to find, I think it's not an optimum idea. They go into /opt//lib, /opt//include, etc. > Adding a special-casing block at the top is almost as easy as adding the > thing

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Tom Russo
On Mon, Dec 18, 2006 at 07:50:32AM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > > Since we only use the "darwin" flag in two places, and since things > like /sw, /opt, and /opt/local wouldn't normally hurt to search on > non-OSX systems, how abou

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Tom Russo
On Mon, Dec 18, 2006 at 07:30:41AM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Mon, 18 Dec 2006, Curt, WE7U wrote: > > > So I see your point Tom... Is there a way we can use > > AC_CHECK_HEADERS() and AC_CHECK_LIB() against non-standard > >

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Tom Russo wrote: > Have a block early on that adds those non-standard locations to LDFLAGS > and CPPFLAGS, e.g. (fudging on syntax here): > > switch ($target) > > > *darwin*) > LDFLAGS="-L/sw/lib $LDFLAGS" > CPPFLAGS="-I/sw/include $CPPFLAGS" > > ... etc. > > AC_CHECK

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Tom Russo
On Mon, Dec 18, 2006 at 07:16:03AM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Mon, 18 Dec 2006, Curt, WE7U wrote: > > > > Of course, that shouldn't happen if we're doing an AC_CHECK_LIB, which > > > will > > > attempt a link --- those shoul

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Curt, WE7U wrote: > So I see your point Tom... Is there a way we can use > AC_CHECK_HEADERS() and AC_CHECK_LIB() against non-standard > locations? My Autoconf/automake/libtool book doesn't go into much > detail on things like this. Maybe the only way to know for sure is > t

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Curt, WE7U wrote: > > Of course, that shouldn't happen if we're doing an AC_CHECK_LIB, which will > > attempt a link --- those should catch the missing "dipstick" issue by > > failing > > to link the conftest. As long as that's what's happening, it's all good. > > But > >

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Mon, 18 Dec 2006, Tom Russo wrote: > But it sounded like what was happening was that Xastir's configure was finding > GraphicsMagick, *NOT* failing during configure, not going on and using > ImageMagick, and then ultimately failing during the final link of Xastir. This may have been a slightly

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Tom Russo
On Mon, Dec 18, 2006 at 06:46:38AM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, 15 Dec 2006, Tom Russo wrote: > > > Apparently, though, GraphicsMagick is still in that state. Either pitch > > GraphicsMagick on Cygwin (if xastir's the onl

Re: [Xastir] cygwin compile problem

2006-12-18 Thread Curt, WE7U
On Fri, 15 Dec 2006, Tom Russo wrote: > Apparently, though, GraphicsMagick is still in that state. Either pitch > GraphicsMagick on Cygwin (if xastir's the only thing that's using it), > downgrade > xorg to the previous version, or force xastir's configure script to ignore > the installed Graphi

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Tom Russo
On Fri, Dec 15, 2006 at 04:00:38PM -0600, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > on 12/15/2006 3:57 PM Curt, WE7U said the following: > >If I type "libdpstk cygwin" into Google I get quite a few hits but > >don't have time to figure out which packa

Re: [Xastir] cygwin compile problem

2006-12-15 Thread J. Lance Cotton
on 12/15/2006 3:57 PM Curt, WE7U said the following: If I type "libdpstk cygwin" into Google I get quite a few hits but don't have time to figure out which package to install. According to: http://www.vips.ecs.soton.ac.uk/index.php?title=Build_on_Cygwin libdpstk (this one is included in versio

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
It should be able to easily find the dipstick; the computer has a webcam on it pointed straight at me :-p -- William McKeehan On Fri, December 15, 2006 4:55 pm, J. Lance Cotton wrote: > on 12/15/2006 3:53 PM William McKeehan said the following: >> I added "libjbig-devel" to my cygwin setup. That

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > I added "libjbig-devel" to my cygwin setup. That takes me to another missing > library. Any ideas where dpstk may live? > If I type "libdpstk cygwin" into Google I get quite a few hits but don't have time to figure out which package to install. -- C

Re: [Xastir] cygwin compile problem

2006-12-15 Thread J. Lance Cotton
on 12/15/2006 3:53 PM William McKeehan said the following: I added "libjbig-devel" to my cygwin setup. That takes me to another missing library. Any ideas where dpstk may live? configure:19039: checking for WriteImage in -lGraphicsMagick configure:19074: gcc -o conftest.exe -g -O2 -pipe -W -Wall

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
I added "libjbig-devel" to my cygwin setup. That takes me to another missing library. Any ideas where dpstk may live? configure:19039: checking for WriteImage in -lGraphicsMagick configure:19074: gcc -o conftest.exe -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -Wno-unused-parameter -

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, Curt, WE7U wrote: > On Fri, 15 Dec 2006, William McKeehan wrote: > > > This looks like the relevant portion of config.log any clues here? > > > > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot > > find -ljbig > > Looking for libjbig.so > > One of t

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > This looks like the relevant portion of config.log any clues here? > > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot > find -ljbig Looking for libjbig.so One of the jpeg libraries I think. -- Curt, WE7U. APRS Client

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
This looks like the relevant portion of config.log any clues here? configure:16572: checking for WriteImage in -lGraphicsMagick configure:16602: gcc -o conftest.exe -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -Wno-unused-parameter -I/usr/local/include -I/usr/X11R6/include -I/usr/

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, J. Lance Cotton wrote: > Look in there for the exact test which failed. I usually find that it's some > other library missing that ImageMagick is dependent upon. That could be the case for GraphicsMagick on his system. Good catch. Not the case for the ImageMagick check thou

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > checking for WriteImage in -lGraphicsMagick... no > configure: WARNING: *** Cannot find GraphicsMagick library files: Building w/o > GraphicsMagick support. *** > checking for Magick-config... no > checking for Magick-config... no > configure: WARNING

Re: [Xastir] cygwin compile problem

2006-12-15 Thread J. Lance Cotton
on 12/15/2006 3:25 PM William McKeehan said the following: Same results: checking for GraphicsMagick-config... yes checking GraphicsMagick/magick/api.h usability... yes checking GraphicsMagick/magick/api.h presence... yes checking for GraphicsMagick/magick/api.h... yes checking for WriteImage in

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
Same results: checking for GraphicsMagick-config... yes checking GraphicsMagick/magick/api.h usability... yes checking GraphicsMagick/magick/api.h presence... yes checking for GraphicsMagick/magick/api.h... yes checking for WriteImage in -lGraphicsMagick... no configure: WARNING: *** Cannot find G

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
Wait a few minutes for the latest configure.ac & acinclude.m4 to show up on anonCVS and then try them. See if anything improves. -- 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 compu

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
I have double and triple-checked the cygwin setup. I believe I have the headers and the library. WhenI do a "ls /usr/lib/*Magick*", here's what I see: /usr/lib/libGraphicsMagick++.a* /usr/lib/libGraphicsMagick.a* /usr/lib/libGraphicsMagick++.dll.a* /usr/lib/libGraphicsMagick.dll.a* /usr/lib/

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, Curt, WE7U wrote: > I also messed up the switchover to ImageMagick during the configure > step and have corrected it in my copy. I'll check that in shortly. Here's what it's doing on my system now: checking for GraphicsMagick-config... no checking for GraphicsMagick-co

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > It does not appear to work with cygwin...unless I've missed some package in > the cygwin install. Might not. Looks like it found GraphicsMagick-config and the header files but not the library itself. I'm working a bit on configure.ac/acinclude.m4 a

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
It does not appear to work with cygwin...unless I've missed some package in the cygwin install. Here's what I see: checking for GraphicsMagick-config... yes checking GraphicsMagick/magick/api.h usability... yes checking GraphicsMagick/magick/api.h presence... yes checking for GraphicsMagick/magic

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > That seems to have fixed it. > > Is GraphicsMagick preferred? If so, I'll remove ImageMagick (I'm pretty sure > I'm only using it for Xastir), install GraphicsMagick and try to rebuild that > way. > > Is there something in cygwin that I need to keep b

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > That seems to have fixed it. > > Is GraphicsMagick preferred? If so, I'll remove ImageMagick (I'm pretty sure > I'm only using it for Xastir), install GraphicsMagick and try to rebuild that > way. It is preferred by me. And by any other developer th

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
That seems to have fixed it. Is GraphicsMagick preferred? If so, I'll remove ImageMagick (I'm pretty sure I'm only using it for Xastir), install GraphicsMagick and try to rebuild that way. Is there something in cygwin that I need to keep back one revision level to make things work with Xastir? I

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > I have both /usr/include/GraphicsMagick/magick/api.h and > /usr/include/magick/api.h (is one from GraphicsMagick, the other from > ImageMagick?). Yep. Add the "--without-graphicsmagick" flag to "./configure" and it'll skip looking for GM and go righ

Re: [Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
As far as I can tell, I do not have GraphicsMagic installed, but the configure script thinks it finds it. It looks like I may have had it installed at one point. It's hard for me to tell for sure with Cygwin...anyone know a definitive way to tell what's installed on Cygwin? I have not updated cygw

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > Anyone noticed a problem with building the current CVS? > > map_geo.c: In function `draw_geo_image_map': > map_geo.c:1907: error: too few arguments to function `GetNumberColors' > map_geo.c:1914: warning: implicit declaration of function `CompressColo

Re: [Xastir] cygwin compile problem

2006-12-15 Thread Curt, WE7U
On Fri, 15 Dec 2006, William McKeehan wrote: > Anyone noticed a problem with building the current CVS? > > map_geo.c: In function `draw_geo_image_map': > map_geo.c:1907: error: too few arguments to function `GetNumberColors' > map_geo.c:1914: warning: implicit declaration of function `CompressColo

[Xastir] cygwin compile problem

2006-12-15 Thread William McKeehan
Anyone noticed a problem with building the current CVS? map_geo.c: In function `draw_geo_image_map': map_geo.c:1907: error: too few arguments to function `GetNumberColors' map_geo.c:1914: warning: implicit declaration of function `CompressColormap' map_geo.c:2117: error: too few arguments to funct