Thanks for the suggestions. I put the modified specs file in the libgcc location and it worked fine if I removed the rule line for pthread. If I simply replaced -lpthread with -lc_r in the specs file, I got all kinds of "reference to compatibility" warnings from libc.so. But if I removed the line (it only expanded to the -lprhread replacement initially), then everything built and the fips_test_suite ran successfully on the target.
Assuming that is ok, then apparently my problem is resolved. Kevin On Wed, Jun 27, 2012 at 12:54 PM, <[email protected]> wrote: > > > ----- Mail original ----- > > De: "Kevin Fowler" <[email protected]> > > À: [email protected] > > Envoyé: Mercredi 27 Juin 2012 17:39:08 > > Objet: Re: help with thread lib - x86/BSD > > > > > > > > > From what I can tell, the specs file is "built-in" to gcc. Yes I can > > look at it with -dumpspecs, and I can override it with, e.g., > > -specs=myspecs, but then I am back to having to modify Configure > > script (and config to point to a new unique platform. I don't think > > gcc automatically loads a specs file from some known location - it > > uses what is built into it or what is specified with the -specs > > option. Maybe there is another way? > > > > # savec original specs > gcc -dumpspecs > myspecsbackup > > # switch to new specs , beware ccache do not have a way to see that change > cat mynewspecs > `dirname $(gcc --print-libgcc-file-name)`/specs > > # restore original specs > cat myspecsbackup > `dirname $(gcc --print-libgcc-file-name)`/specs > > Gilles > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [email protected] > Automated List Manager [email protected] >
