Hmmm, why should you have a PIC test? Who cares if something has PIC or not? You only thing you care about is that you CAN do what you want to do with it? (In this case I think it is simply that you can build an executable using a shared library PLUS the given library you are testing.)
Barry configure is suppose to be "can I ...?" not "is something ...?" On Tue, 13 Dec 2005, Matthew Knepley wrote: > I have been on Google tonight, and still cannot find any information > about testing for PIC code. This has to be the worst compiler decision > ever, except maybe static/shared libraries. Anybody with test ideas? > > Matt >
