longj@lonex.radc.af.mil (Jeffrey K. Long) (11/17/90)
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
entropy@mole.ai.mit.edu (Nick Castellano) (11/18/90)
In article <1990Nov16.211558.14374@lonex.radc.af.mil> longj@lonex.radc.af.mil (Jeffrey K. Long) writes: >attempts. The UNIXMODE trick mentioned by Doug S. seemed to have helped >also. I saw that message about UNIXMODE -- it didn't describe what all of the symbols in the variable mean, though. Could someone post some kind of doc on UNIXMODE -- i.e. what programs use it, and what various values in it do? Thanks, nick -- | | | entropy@mole.ai.mit.edu | | | ncastellano@{eagle.wesleyan.edu, wesleyan.bitnet} / | \ Sinkhole!dEADHEAd[@mast.citadel.moundst.mn.org] (call 203-873-8518) / | \ Boycott Lotus, Apple, Ashton-Tate, and Xerox! Join the LPF!
gaudreau@juggler.East.Sun.COM (Joe Gaudreau - Sun BOS Software) (11/19/90)
Humble beginnings... Can someone provide me with a pointer to a file (or other info) on how to get a working Gnu C, C++, Emacs, etc, etc system going? Where to get it, where to put it, what to tell it and so on (and you tell two friends, and they tell two friends, ...). I'm sort-of aware that atari.archive has the "stuff" but I don't know how to set it up... Any help would be appreciated! Cheers, Joe -=-
gjh@hplb.hpl.hp.com (Graham Higgins) (11/20/90)
++ Humble beginnings... Can someone provide me with a pointer to a file ++ (or other info) on how to get a working Gnu C, C++, Emacs, etc, etc ++ system going? Where to get it, where to put it, what to tell it and ++ so on (and you tell two friends, and they tell two friends, ...). I'm ++ sort-of aware that atari.archive has the "stuff" but I don't know how ++ to set it up... Hang fire Joe, that's exactly what I'm trying to do. Having a few problems at the moment though. Cheers. Graham
dstailey@gnu.ai.mit.edu (Doug Stailey) (11/25/90)
In article <1990Nov16.211558.14374@lonex.radc.af.mil> longj@lonex.radc.af.mil (Jeffrey K. Long) writes: >I finally got GCC v1.37.1 working here at work!! Glad to hear it! >no more "game machine" >cracks! Really glad to hear it! >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?? > I, too, noticed that the VDI cursor control routines are missing from the GCC GEM libs. After searching the libs with the archiver and namer, I am now certain they are not there. At this point, I can only recommend getting the sources necessary to make gem.olb, and adding the four missing calls to the ROM code yourself. One day soon, I am going to do this too. -- disclaimer: This message is sold by weight, not volume. Contents may have settled during shipment.
dstailey@gnu.ai.mit.edu (Doug Stailey) (11/25/90)
In article <ENTROPY.90Nov17174003@mole.ai.mit.edu> entropy@mole.ai.mit.edu (Nick Castellano) writes: >In article <1990Nov16.211558.14374@lonex.radc.af.mil> longj@lonex.radc.af.mil (Jeffrey K. Long) writes: >>attempts. The UNIXMODE trick mentioned by Doug S. seemed to have helped >>also. > >I saw that message about UNIXMODE -- it didn't describe what all of >the symbols in the variable mean, though. Could someone post some >kind of doc on UNIXMODE -- i.e. what programs use it, and what various >values in it do? > >Thanks, > nick The file UNIXMODE.doc is available at cs.uni-sb.de. Anyone who is interested, and cannot reach this site, can mail me at dstailey@gnu.ai.mit.edu, and I will send them a (compressed, uuncoded) copy. The file is about 10K in this format. Good Luck, Doug -- disclaimer: This message is sold by weight, not volume. Contents may have settled during shipment.