Properly handle several --without options during configure

Some of the --with-* options that are processed during configure time do not properly handle the corresponding --without options and will crash when processed (For example, --without-version-string), in other more misleading cases the --without-* option may make sense to pass but will actually silently produce incorrect results if they are (For example, --without-build-user and all the --with-vendor-* options). The most elegant way to solve this would simply be to handle such cases and display warnings when they're encountered (or if the option is critical to the build process, throwing an error)