curl 7.42 build fails at configure stage if the following options are used : GSSAPI_BASE for the port WITHOUT_KERBEROS=true and WITH_GSSAPI=true for the base system According to the src.conf man page, the latter is a legitimate combination but curl seems to assume that gssapi implies kerberos. From config.log : configure:4218: checking whether the C compiler works configure:4240: cc -I/usr/include -O2 -pipe -march=core2 -fstack-protector -fno-strict-aliasing -I/usr/include -I/usr/include -L/usr/lib -L/usr/lib -L/usr/lib -Wl,-rpath,/usr/lib:/usr/local/lib -L/usr/lib -Wl,-rpath,/usr/lib:/usr/local/lib -fstack-protector conftest.c -lkrb5 -lgssapi -lgssapi_krb5 -lkrb5 -lgssapi -lgssapi_krb5 >&5 /usr/bin/ld: cannot find -lkrb5 cc: error: linker command failed with exit code 1 (use -v to see invocation)
The default configuration is "GSSAPI w/ KERBEROS in base system and GSSAPI_BASE for ftp/curl". You cannot use GSSAPI_BASE if you built base system with WITHOUT_KERBEROS defined. I would change GSSAPI_BASE_DESC to "GSSAPI support via base system (Kerberos required)" to make it more clear.
GSSAPI_BASE_DESC changed to "GSSAPI support via base system (Kerberos required)" in r385944.