From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en] (X11; U; SunOS 5.6 sun4u)
Description of problem:
using the same cache speeds up the configure for db significantly (at least
on my solaris box) and has the added bonus of passing a working compiler to
db (the db configure uses a hack to make it prefer cc to gcc, but doesn't
catch the case where cc is a stub the way AC_PROG_CC does.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. with a broken cc and working gcc run configure
Created attachment 31258 [details]
patch using different args to db3/configure
Yes, db3 uses a separate config.cache. That is by intent.
Nothing wrong with your patch however, just not how I wish
Berkeley DB wired in rpm.