Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!cs.utexas.edu!sun-barr!lll-winken!ncis.tis.llnl.gov!blackbird!lonex.radc.af.mil!longj
From: longj@lonex.radc.af.mil (Jeffrey K. Long)
Newsgroups: comp.sys.atari.st
Subject: GCC V1.37.1 Lives (and Thanks to many!!)
Message-ID: <1990Nov16.211558.14374@lonex.radc.af.mil>
Date: 16 Nov 90 21:15:58 GMT
References: <1990Nov16.003735.14049@contact.uucp>
Sender: Jeff Long
Distribution: na
Organization: RADC
Lines: 32

I finally got GCC v1.37.1 working here at work!! It sure went through some
tricky code that I thought I was going to spent several days debugging
very easily!!  Only a few minor changes and complied all the stuff I wanted!!
This, combined with the gnumake facility, gulam, and gdb, have made 
true belivers of my fellow engineers here at work, no more "game machine"
cracks!  

Thanks to Doug Stailey, Roy Bixler and David Mak for responding to my pleas
for help!!  It turned out to be a combination of several problems (isn't
it always??).....I had several corrupted files that took many transfers from
host to ST to get correctly, some which didn't survive well on the first
attempts.  The UNIXMODE trick mentioned by Doug S.  seemed to have helped
also.

NOW THAT I HAVE BUTTERED EVERYONE UP......

I have a program that uses a lot of VDI screen routines.  After compiling
it up, I still can't get the linker to resolve the following symbols:
v_curhome    v_curdown   v_enter_cur   v_exit_cur

Are these not in the gem.olb ??  I had several other vdi calls that
were unrecognized until I remembered to link in the gem.olb, but these
four remained?  

Any suggestions??


-- 
-----------------------------------------------------------------------
Capt Jeff Long                         Rome Air Development Center
longj@lonex.radc.af.mil                Network Design Laboratory
jlong@cassiopeia.radc.af.mil           (315)330-7751 or (DSN)587-7751