Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!mailrus!cornell!uw-beaver!ssc-vax!bcsaic!paula
From: paula@bcsaic.UUCP (Paul Allen)
Newsgroups: comp.os.minix
Subject: Re: Liborders, reboots and a mundane matter
Message-ID: <27507@bcsaic.UUCP>
Date: 5 Jul 90 19:29:49 GMT
References: <23637@nigel.udel.EDU>
Organization: Boeing Computer Services AI Center, Seattle
Lines: 25

I'm following-up rather than mailing because there may be others who
share this misunderstanding about rebuilding libc.a.  (Please note
that it's OK to misunderstand!  Sometimes my life seems to be one big
misunderstanding, but we won't go into that...   :-) )

In article <23637@nigel.udel.EDU> AJB@dlvh.daresbury.ac.uk writes:
>  My conceptual problem is basically this:
>   When you're upgrading Minix you recompile OTHER/ANSI/POSIX etc using
>   your current libc.a
>   Changes in the source libraries are therefore compiled using the 'old'
>   libc.a and therefore incorporate machine code from that library.

What's missing here is the fact that libc.a is only used at link time.  
When you compile the library sources you're only making new object files, 
not new executables.  Unless you keep old library object files around,
it's not possible for a new libc.a to be contaminated by traces of any
previous one.

Paul Allen


-- 
------------------------------------------------------------------------
Paul L. Allen                       | pallen@atc.boeing.com
Boeing Advanced Technology Center   | ...!uw-beaver!bcsaic!pallen