Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!pacific.csl.uiuc.edu!steven
From: steven@pacific.csl.uiuc.edu (Steven Parkes)
Newsgroups: comp.sys.mips
Subject: Re: BSD43 libraries
Message-ID: <1990Jun1.200430.14118@ux1.cso.uiuc.edu>
Date: 1 Jun 90 20:04:30 GMT
References: <1990May17.201954.13301@maverick.ksu.ksu.edu> <1990Jun1.132149.29655@maverick.ksu.ksu.edu> <39200@mips.mips.COM>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: steven@pacific.csl.uiuc.edu
Organization: Coordinated Science Laboratory
Lines: 13


|> One possible one that bites us
|> occasionally when working on a single program being compiled twice with
|> two different -systypes (we do tar this way), is that you get a stale
|> .o compiled for the other systype, and when everything is bound into
|> an executable, it typically core dumps due to library and include
|> file mismatches.

Is there anyway to tell what systype a .o was compiled for? (i.e. via nm, etc)

|> Jay McCauley

Same one that used to work at Zilog?