Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!nic.csu.net!csun!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Problems with Slibcfp.a
Message-ID: <1991Feb21.195320.15498@kithrup.COM>
Date: 21 Feb 91 19:53:20 GMT
References: <5011@vela.acs.oakland.edu> <1108@pemcom.pem-stuttgart.de>
Organization: Kithrup Enterprises, Ltd.
Lines: 21

In article <1108@pemcom.pem-stuttgart.de> alfred@pemcom.pem-stuttgart.de (Alfred Koebler) writes:
>To solve this problem, the linker had always to use Slibcfp.a

Well, that's not what the system C compiler does.  It spits out something
like

	Slibcfp.a Slibc.a

There is a symbol, uhm, uhm, __fltused, I think, which is defined as an
external if the code uses floating point.  Slibcfp.a has the various
routines that use floating point with __fltused defined.  (Note that
*printf* isn't defined until Slibc.a, and it declares __doprnt as an
external there.)

Aren't linkers *fun*?

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.