From owner-freebsd-ports@FreeBSD.ORG  Sat Mar 19 01:38:08 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6BFB216A4CF; Sat, 19 Mar 2005 01:38:07 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 22F6243D49; Sat, 19 Mar 2005 01:38:07 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id A9367149BA; Fri, 18 Mar 2005 19:38:06 -0600 (CST)
Date: Fri, 18 Mar 2005 19:38:06 -0600 (CST)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Adam Weinberger <adamw@FreeBSD.org>
In-Reply-To: <423B6523.5090904@FreeBSD.org>
Message-ID: <Pine.LNX.4.44.0503181929500.13080-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org>
cc: freebsd-ports@freebsd.org
Subject: Re: Max recursion level (500) exceeded.
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2005 01:38:08 -0000

On Fri, 18 Mar 2005, Adam Weinberger wrote:

> The problem lies in the gcc32 port. It redefines USE_GCC. It, and the 
> other gcc ports, need not to do that.

IIRC gcc3.2 had a USE_GCC definition that its internal make stuff
needed whose existance predated the creation of bsd.gcc.mk which
introduced a USE_GCC variable intended to be used internal to the
ports framework which has different semantics.  AFAIK gcc32 has
been broken since that time.

I do not have time to test this hypothesis but would suggest trying
a patchset with s/USE_GCC/INTERNAL_USE_GCC/ or something.

It would be great if someone could investigate and fix this problem ...

mcl