In article <20060721114142.GA3195@britannica.bec.de> Joerg wrote:
: On Thu, Jul 20, 2006 at 10:41:53PM +0200, Dieter Baron wrote:
: >   Could we *please* fix these problems *before* committing these kind
: > of changes?  While the change is correct and good, randomly breaking
: > packages and expecting others to fix them is not.

: This is not active by default yet.

-# Always require a C compiler for proper compiler detection.
+# Since most packages need a C compiler, this is the default value.
 USE_LANGUAGES?=        c
-.if empty(USE_LANGUAGES:Mc)
-USE_LANGUAGES:=        c ${USE_LANGUAGES}
-.endif

  So, for any package that has
	USE_LANGUAGES=c++
C is no longer added to the list of needed languages.  So any C++
using package that needs (e. g. in its configure script) a C compiler
but does not explicitly say so is now broken.

  Just how is this not active yet?

					yours,
					dillo