Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!cs.utexas.edu!uunet!mcsun!hp4nl!star.cs.vu.nl!jms
From: jms@cs.vu.nl (Jan-Mark)
Newsgroups: comp.os.minix
Subject: Re: Compaction in Minix  ( Novice Question)
Message-ID: <8387@star.cs.vu.nl>
Date: 29 Nov 90 16:29:15 GMT
References: <11362@ccncsu.ColoState.EDU>
Sender: news@cs.vu.nl
Reply-To: jms@cs.vu.nl (Jan-Mark Wams)
Organization: VU Dept. of Computer Science, Amsterdam, The Netherlands
Lines: 28

In article <11362@ccncsu.ColoState.EDU>,
	mannemel@handel.cs.colostate.edu (devakumar mannemela) writes:
> 
> now i tried to add it to libc.a , in the following manner.
> 
> ar rb uniqport.s libc.a compact.s
...
> Now compact.s is the first thing in libc.a  .
...
>  	unresolved references
> 	-compact
...
> That was the result. Isn't it supposed to recognise compact by checking in 
> libc.a ? 
> 

	Try compiling compact with the -LIB option, this will add a
	``.define _compact'' to compact.s. The normal ``.glob _compact''
	isn't innough for a function in a lib. You can check if you have
	got the define there, by looking at the output of ``libupack <
	compact.s.''

	Jan-Mark.
--

				 (:>	jms
				(_)
			========""======