Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!mips!winchester!jay
From: jay@mips.COM (Jay McCauley)
Newsgroups: comp.sys.mips
Subject: Re: BSD43 libraries
Message-ID: <39238@mips.mips.COM>
Date: 4 Jun 90 16:46:14 GMT
References: <1990May17.201954.13301@maverick.ksu.ksu.edu> <1990Jun1.132149.29655@maverick.ksu.ksu.edu> <39200@mips.mips.COM> <1990Jun1.200430.14118@ux1.cso.uiuc.edu>
Sender: news@mips.COM
Reply-To: jay@mips.COM (Jay McCauley)
Organization: MIPS Computer Systems, Inc.
Lines: 26

In article <1990Jun1.200430.14118@ux1.cso.uiuc.edu> steven@pacific.csl.uiuc.edu writes:
>
>|> 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)
None that I know of.  Sounds like an RFE, I'll ask the compiler folks about it.
Future work in support of dynamic linking does fairly extensive checking
of this sort of thing, although I am not sure about the -systype specifically.
I think that check is implicit in matching up to the right shared lib.
>
>|> Jay McCauley
>
>Same one that used to work at Zilog?
Jay, glancing furtively, says, "Yes, but I've changed."  (how's that for
a reply that covers all possible questions?)  That was A LONG time ago
by Silly Con valley standards.
Jay
-- 
Jay McCauley
MIPS Computer Systems, 928 E. Arques, Sunnyvale, CA 94086 (408)524-8211
{decwrl,pyramid,ames}!mips!jay         jay@mips.com