Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!Teknowledge.COM!unix!hplabs!hpfcso!aoe
From: aoe@hpfcso.HP.COM (Alexander Elkins)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Creating SAS C-run Time librarys! Help
Message-ID: <101060004@hpfcso.HP.COM>
Date: 14 Jan 91 23:44:12 GMT
References: <1991Jan13.143749.46649@cc.usu.edu>
Organization: Hewlett-Packard, Fort Collins, CO, USA
Lines: 41

>   	I am using the new SAS C v5.10 and have had a few problems with trying
>   to build the library. 
>
>    	BLINK LIBFD MyLib.fd to MyLib.library from libent.o+libinit.o+MyLib.o
>    (I am not sure which order the Libent.o and Libinit.o go in right now but I
>    used the order from the manual.)

You got the order right.  The manual uses spaces instead of '+' characters.

>    	I get a list of blink errors. They are
>
>   	1) Enter a DEFINE value for __xcovf (default _stub)
>   	2) Enter a DEFINE value for _LibName (default _stub)
>	3) Enter a DEFINE value for _LibID (default _stub)   
>
>  	and so on. When I try to define the names from that point the system
>  tells me that "MyLib.library" is an unknow symbol. So my question. Where do I
>   define all of these wonderfull things and what in the world is __xcvof?

__xcvof is jumped to if your stack overflows.  Compile with "-v" option
to avoid needing this (turns off stack checking).

Use "-u" flag when assembling libent.a which adds the additional leading '_'
you are missing.  Also note that you must also use "-ml"
(that a lowercase 'L' not the number one!) and "__saveds" when compiling.

Typical function (don't use __regargs):

int __saveds __asm test(register __d0 int i)
{
	/* rest of code */
	return 0;
}

>   	Any help would be greatly appriciated..
>
>   	Thanks,
>   	joshua
>   	SLMT9@cc.usu.edu

 - Alexander Elkins (aoe@hpfiaoe.fc.hp.com)