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] Maybe its me but . . .Kubuntu - xastir 1.85

2007-01-12 Thread Tom Russo
On Fri, Jan 12, 2007 at 01:44:30PM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, 12 Jan 2007, Victor wrote: > > > After receiving a message if I close the box using the close "button" > > the program closes. If I close the box by closing

Re: [Xastir] Maybe its me but . . .Kubuntu - xastir 1.85

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Victor wrote: > After receiving a message if I close the box using the close "button" > the program closes. If I close the box by closing the window ("x") > it works fine. Anyone else have this? Yes. With Lesstif and the Send Message box. If you compile with OpenMotif or

[Xastir] Maybe its me but . . .Kubuntu - xastir 1.85

2007-01-12 Thread Victor
After receiving a message if I close the box using the close "button" the program closes. If I close the box by closing the window ("x") it works fine. Anyone else have this? Scott Moore W1SSN ___ Xastir mailing list Xastir@xastir.org http://lists

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] segfault

2007-01-12 Thread Tom Russo
On Fri, Jan 12, 2007 at 12:46:28PM -0800, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, 12 Jan 2007, Curt, WE7U wrote: > > > Look for __LSB__ in messages_gui.c and you'll see where I did > > exactly this fix for the LSB version. > > > > If we had

Re: [Xastir] segfault

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Curt, WE7U wrote: > Look for __LSB__ in messages_gui.c and you'll see where I did > exactly this fix for the LSB version. > > If we had a hook whereby we could tell whether we were compiled with > Lesstif or Motif, we could do the same thing for Lesstif and solve > this segfau

Re: [Xastir] segfault

2007-01-12 Thread Curt, WE7U
On Thu, 11 Jan 2007, Tom Russo wrote: > Just began to look into those segfaults tonight. I can reliably crash > xastir (built with lesstif) by repeatedly opening the send-message dialog > and changing the format between d700/hamhud/d7, then closing the dialog. > > The segfault is in a free, down

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] segfault

2007-01-12 Thread Curt, WE7U
On Thu, 11 Jan 2007, Tom Russo wrote: > Just began to look into those segfaults tonight. I can reliably crash > xastir (built with lesstif) by repeatedly opening the send-message dialog > and changing the format between d700/hamhud/d7, then closing the dialog. > > The segfault is in a free, down

Re: [Xastir] Wiki changes reflecting lesstif/openmotif segfault issues.

2007-01-12 Thread Curt, WE7U
On Fri, 12 Jan 2007, Tom Russo wrote: > If you've not been following, it's been seen that the LessTif library > can cause xastir to crash under certain circumstances. > > Pending fixes for that, I've updated two of the Wiki pages to suggest using > openmotif instead. Definitely good changes to ma

Re: [Xastir] Broken

2007-01-12 Thread Curt, WE7U
On Thu, 11 Jan 2007, Chip G. wrote: > So I also fixed my CVS problem by deleting everything and starting > from scratch (including commenting out my entire cvsrc file which > somehow seemed to be munging things up, or at least it suddenly > stopped hanging midway through when I commented out every

re: [XASTIR] segfault

2007-01-12 Thread kent noonan
> I am getting segfault from xastir. I am running CVS as of about 2:30 on 1/10. > After I start xastir and it runs for a little while so I have weather alerts, > I go to the window for weather alerts. I can scroll around all I want, but if > I click on one to finger wserver , close that window a

[Xastir] Wiki changes reflecting lesstif/openmotif segfault issues.

2007-01-12 Thread Tom Russo
If you've not been following, it's been seen that the LessTif library can cause xastir to crash under certain circumstances. Pending fixes for that, I've updated two of the Wiki pages to suggest using openmotif instead. On the wiki page "HowTo:Ubuntu 6.10" I now specify the relevant OpenMotif li