Subject: Re: Using same .o files for pic/non-pic libraries.
To: Simon Burge <simonb@netbsd.org>
From: Ignatios Souvatzis <is@jocelyn.rhein.de>
List: tech-toolchain
Date: 09/12/1999 22:42:14
On Sat, Sep 11, 1999 at 10:59:42PM +1000, Simon Burge wrote:
> Folks,
> 
> I don't know if this can be put to a practical use, but on the pmax (and
> other mips ABI platforms) the .o and .so files generated during library
> builts are exactly the same - it seems a little bit silly to compile
> everything twice when we really don't need to.
> 
> A simple test would be if both CPICFLAGS and APICFLAGS are empty, then
> we could depend the .so on the .o and then symlink to the .o.  Does this
> seem workable?

You're trying to get an advantage for your machines, in the "make
build" benchmark, right?

	-is