search for: ranlibflag

...unny results. To make matters worse, there does not seem to be an exhaustive list of environment variables to check, at least not for gcc and autoconf (though there are plenty of non-exhaustive ones). I know I have to check CC, CXX, CCFLAGS, CPPFLAGS, CXXFLAGS, and LDFLAGS; does an ASFLAGS exist? A RANLIBFLAGS? ARFLAGS? (This is essentially the same problem as with global variables: lack of information hiding, making it very difficult to check all dependencies.) I'm pretty sure that I'm not the first to observe this kind of difficulty, and the GNU project probably won't change their convent...

Hi Jo, > No, that was written under the assumption that passing in CC and CXX > via env variables wouldn't work. Things work now, so that assumption > is obviously wrong. > > I still don't like environment variables. They tend to remain in > effect long after I forgot that I set them, creating all sorts of > hassle. In fact I suspect I already fell prey to this,

Am Montag, den 24.03.2008, 12:06 -0700 schrieb Tanya M. Lattner: > > This is close to a showstopper for integrating an llvm-gcc bootstrap > > into the nightly tester. The llvm-gcc ./configure needs to be called > > very differently from the llvm ./configure, and keeping two sets of > > options is Not Worth The Trouble, at least IMHO. > > So you didn't like the