Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!mcnc!rti!mozart!walker
From: walker@unx.sas.com (Doug Walker)
Newsgroups: comp.sys.amiga
Subject: Re: SAS C 5.10 problems
Message-ID: <1990Nov26.195620.20069@unx.sas.com>
Date: 26 Nov 90 19:56:20 GMT
References: <9011081128.AA14500@bisco.kodak.COM>
Organization: SAS Institute Inc.
Lines: 31

In article <9011081128.AA14500@bisco.kodak.COM> nobody@Kodak.COM writes:
>Since it would take me days to figure out how to get back to a CBM
>shell, 

Why would it take you 'days'?  What's wrong with "NewShell"?  There
have been MANY reports of problems with AShell, not just with the
compiler.  I recommend looking at WShell from Bill Hawes.

>C program scattered about many files, during link I get "undefined
>symbols" such as _CXV53, _CXD54, etc.  I can't find the correct options
>to get the compiler to produce an assembly listing so that I can look
>for these, or figure out any other way to track them down.  Help?

You have to link with the floating point libraries if you use any
floating point variables.  'lc' will do this automatically if
you specify a floating point option (like -ff) or you can tell it
to do it by specifying -Lm instead of -L.  If you don't use lc,
BLink with the math library BEFORE the normal lc.lib or lcr.lib or
whatever you use.  See the 5.10 update documentation, pages
G20-9 and G20-10 for more information on which library to use 
for your options.  (If you aren't using any floating point options,
use lcm.lib and lc.lib ; remember that lcm.lib comes FIRST on the
link line.)


  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: ...mcnc!rti!sas!walker   plink: dwalker  bix: djwalker