Noticed this when I had a typo on the configure command line. The configure
script does not catch the following bogus option:
--enable-bogosity
That might seem like no biggie, but it also doesn't seem to notice this
error:
--enable-thread-safeyt (notice the mispelling)
Makes it look like you had a valid configure.