Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!ukc!dcl-cs!strath-cs!paisley!rh
From: rh@cs.paisley.ac.uk (Robert Hamilton)
Newsgroups: comp.sys.atari.st
Subject: Re: need help: lattice c gem access
Message-ID: <371@paisley.ac.uk>
Date: Wed, 9-Sep-87 04:58:14 EDT
Article-I.D.: paisley.371
Posted: Wed Sep  9 04:58:14 1987
Date-Received: Sat, 12-Sep-87 04:43:10 EDT
References: <285UD138985@NDSUVM1> <5238@jhunix.UUCP>
Reply-To: rh@cs.paisley.ac.uk (Robert Hamilton)
Organization: Paisley College of Technology.
Lines: 22
Keywords: Lattice C  GEMLIB.H

In article <5238@jhunix.UUCP> ins_bjjb@jhunix.UUCP (Jared J Brennan) writes:
>In article <285UD138985@NDSUVM1> UD138985@NDSUVM1.BITNET writes:
>>I have been trying to use some simple Lattice C GEM ruotines.  Everything
>>compiles fine, but when I try to link, all of my GEM calls turn up as
>>undefined symbols.  I am linking with the C.LNK file that came with the

This is an annoying feature in lattice if you dont know about it.
In the pre 3.4 lattice the gem library was compiled with the 8 character
symbol limit so "appl_init" is "appl_ini" .
This is ok unless you use the -n option in your own progs. So don't use
the -n option
In 3.4 If I remember things are reversed so "appl_init" really is "appl_init"
and you have to use use the -n  option.

I wrote to the net a while back about the new lattice linker bombing out.
I've seen no replies. Have I just been unlucky?

-- 
JANET:  rh@uk.ac.paisley.cs		| Computing Science
EMAIL:	rh@cs.paisley.ac.uk		| Paisley College
UUCP:	...!seismo!mcvax!ukc!paisley!rh	| High St., Paisley
Phone:	+44 41 887 1241 Ext. 219	| Scotland , PA12BE