[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
nathan r. hruby nhruby@uga.edu
Tue, 25 May 2004 09:29:02 -0700 (PDT)
On Tue, 25 May 2004, Bryan Stansell wrote: > On Tue, May 25, 2004 at 08:43:55AM -0400, nathan r. hruby wrote: > > OTOH, I did discover that if you run ./configure --with-openssl and > > ./configure can't seem to make openssl work, it will happily continue to > > build, removing the openssl option and issue no errors :( Is there any > > way we can have ./configure either emit a loud warning or simply die if > > --with-openssl is specified but the configure tests don't pass? > > personally, i'm a fan of having it continue if it can't find the > necessary files (and my experience with other configure-based apps says > that's the "normal" way of behaving, though i have seen some abort. the > whole idea for using configure is to auto-detect what it can and just > live with the results). but, i do believe it would be nice to see what > happened in a nice, concise way. so, how about a summary at the end of > the configure run: > [snip] Looks great, works for me! -n -- ------------------------------------------- nathan hruby <nhruby@uga.edu> uga enterprise information technology services production systems support metaphysically wrinkle-free -------------------------------------------