On Dec 29, 2006, at 4:16 PM, Curt Mills wrote:
On Fri, 29 Dec 2006, g1ixv wrote:
Got the same error message here on Suse 9.3
That's life on the bleeding edge. Was fixed about the time I saw
your message come across.
I was getting worried that I HADN'T seen that error! I finally got
On Fri, Dec 29, 2006 at 06:44:15PM -0800, we recorded a bogon-computron
collision of the <[EMAIL PROTECTED]> flavor, containing:
> On Fri, 29 Dec 2006, Mike Fenske wrote:
>
> > I haven't seen a compile error with Xastir for a _long_ time, but
> > with today's CVS, I got one. Looks like the new co
On Fri, 29 Dec 2006, Mike Fenske wrote:
> I haven't seen a compile error with Xastir for a _long_ time, but
> with today's CVS, I got one. Looks like the new code Curt has
> added tor printing. Running SuSE 7.3 here.
Yep. Any time you see some _new_ code get added there's a good
possibility that
On Fri, 29 Dec 2006, g1ixv wrote:
> Got the same error message here on Suse 9.3
That's life on the bleeding edge. Was fixed about the time I saw
your message come across.
--
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto: A tax on people
I haven't seen a compile error with Xastir for a _long_ time, but with today's
CVS, I got one. Looks like the new code Curt has added tor printing. Running
SuSE 7.3 here.
Mike Fenske
VE7MKF
make[3]: Entering directory `/home/mike/src/xastir/src'
source='maps.c' object='maps.o' libtool=no \
depf
On Fri, 29 Dec 2006, Chip G. wrote:
> I see a number of options which can be configured by un-commenting
> some lines and recompiling. Is there a reason why these are not available as
> options via the Configure menu? I suppose some might be easier to code based
> on changing only at compile-time,
I have been brushing up on my C skills and so I was venturing into
the source folder for Xastir. When I looked in the main.c I
immediately started wondering. I see a number of options which can be
configured by un-commenting some lines and recompiling. Is there a
reason why these are not av
[EMAIL PROTECTED] wrote:
Got a build error with this morning's "cvs update" Saw this on both
RedHat 9, Mac OS X 10.4.8. Trying CygwinX, but cvs update appears to be
hanging.
--
Dan Brown
[EMAIL PROTECTED]
Got the same error message here on Suse 9.3
Colin G1IXV
On Fri, 29 Dec 2006, Dan Brown wrote:
> Installing ghostview also appears to have fixed it here.
With the latest committed changes I can comment out the lines in
config.h that refer to GV or LPR, recompile, and get popup messages
when I try to print or print preview.
I still need to figure out w
On Fri, 29 Dec 2006, Curt Mills wrote:
> On Fri, 29 Dec 2006, Curt Mills wrote:
>
> > I think something like "#ifdef GV_PATH" and "#ifdef LPR_PATH" will
> > do it.
>
> Am committing fixes to maps.c and xa_config.c that should fix this.
Installing ghostview also appears to have fixed it here.
On Fri, 29 Dec 2006, Curt Mills wrote:
> I think something like "#ifdef GV_PATH" and "#ifdef LPR_PATH" will
> do it.
Am committing fixes to maps.c and xa_config.c that should fix this.
--
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto: A
On Fri, 29 Dec 2006, Dan Brown wrote:
> maps.c: In function 'Print_postscript_destroy_shell':
> maps.c:3871: error: 'GV_PATH' undeclared (first use in this function)
I'm still in the middle of making changes. Actually just started to
get worthwhile functionality last night at about 11pm, so comm
On Fri, 29 Dec 2006, Dan Brown wrote:
>
>
>
> Got a build error with this morning's "cvs update" Saw this on both
> RedHat 9, Mac OS X 10.4.8. Trying CygwinX, but cvs update appears to be
> hanging.
Cygwin appeared to go just fine.
--
Dan Brown
[EMAIL PROTECTED]
On Dec 29, 2006, at 4:27 AM, [EMAIL PROTECTED] wrote:
Curt Mills wrote:
I think this is only for the Intel Mac's?
It's conceivable to have it run on PPC macs - there was a product
called
VirtualPC thatwould allow intel emulation on PPC macs. Microsoft
assimilated the company, and I nev
Got a build error with this morning's "cvs update" Saw this on both
RedHat 9, Mac OS X 10.4.8. Trying CygwinX, but cvs update appears to be
hanging.
--
6) Removing autom4te.cache directory...
5) Running aclocal...
4) Running autoheader...
3) Running autoconf...
2
Curt Mills wrote:
> I think this is only for the Intel Mac's?
It's conceivable to have it run on PPC macs - there was a product called
VirtualPC thatwould allow intel emulation on PPC macs. Microsoft
assimilated the company, and I never got the microsoft branded virtual PC
to work reliably with
16 matches
Mail list logo