I have both WITH_CLANG_IS_CC and WITHOUT_GCC set in /etc/src.conf, so gcc does not exist in the base system. Any port that has USE_GCC=4.2+ set incorrectly assumes that GCC 4.2 is in base. I think the expected behaviour should be to identify that it could be in base, then check, rather than simply taking it on faith that /usr/bin/gcc exists. Fix: wrap setting _GCCVERSION and _GCC_FOUND${v} in .if directives and remove the error condition if _GCCVERSION is undefined. I attached a patch. Patch attached with submission follows: How-To-Repeat: Build a release WITHOUT_GCC and WITH_CLANG_IS_CC and then try to build a port with USE_GCC=4.2+ (for example audio/clementine-player).
Fix Summary and assign.
I believe this bug can be closed, gcc has not been built by default on 10/head for amd64/i386 since a few months
I am sorry this got stuck "in the system", but luckily it seems to have been addressed in between already by r313323 | gerald | 2013-03-03 03:21:29 +0000 (Sun, 03 Mar 2013) | 10 lines Do not just rely on the version number of FreeBSD in deciding whether a certain version of GCC is in the base, but also check the existence of /usr/bin/gcc. This unbreaks systems where GCC is not built as part of the world, and instead relies on versions of GCC in the Ports Collection there. PR: 175252 Submitted by: Yamaya Takashi <yamayan@kbh.biglobe.ne.jp> If this patch does not solve the issue you saw, can you please advise and I'll have another look?