Newsgroups: comp.sys.atari.st
   From: b...@cwruecmp.UUCP (Jwahar R. Bammi)
   Date: Tue, 19-May-87 18:24:23 EDT
   Subject: Re: Alcyon C printf (again)

   In article <870518190028.128...@RADC-MULTICS.ARPA>
   P...@RADC-MULTICS.ARPA (Rodney) writes:

   >  Ok, here we go again.  After my last request for information about
   why
   >the printf function DOESN'T WORK in alcyon C, I received many replies

   >which said that they just used sprintf + Cconws.

   I dunno. Printf always worked for me. I assume you have v4.14 of the
   compiler and the new libraries that came with it.

   If you are using the motorola fast floating point libraries, ie.  you
   are specifying the `-f' option to C068,  link as follows

           lo68 -r -s -o foo.68k gemstart.o foo.o gemlib libf
     or
           link68 foo.68k=gemstart,foo,gemlib,libf

   If you are using the IEEE floating point libraries, ie. you DO NOT
   specify the `-f' option to C068, link as follows

           lo68 -r -s -o foo.68k gemstart.o foo.o libm gemlib
     or
           link68 foo.68k=gemstart,foo,libm,gemlib

   Note that libm comes before gemlib, otherwise you pick up the
   incorrect version of printf from gemlib for the IEEE format.

   If you are using no floating point, AND you are compiling with the
   `-f' option, you can skip linking in libf by defining dummy etoa,
   ftoa, atof symbols, thereby satisfying the linker, and saving
   yourself a couple of bytes.
   hope that helps,

   -- usenet: {decvax,cbatt,cbosgd,sun}!cwruecmp!bammi
   jwahar r.  bammi csnet:       bammi@case arpa:
   bammi%case@csnet-relay compuServe:  71515,155
.