Subject: Using same .o files for pic/non-pic libraries.
To: None <tech-toolchain@netbsd.org>
From: Simon Burge <simonb@netbsd.org>
List: tech-toolchain
Date: 09/11/1999 22:59:42
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?

Simon.