From owner-freebsd-ports Wed Mar 18 08:38:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07003 for freebsd-ports-outgoing; Wed, 18 Mar 1998 08:38:01 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from ppp6529.on.bellglobal.com (ppp6529.on.bellglobal.com [206.172.208.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06978 for ; Wed, 18 Mar 1998 08:37:54 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by ppp6529.on.bellglobal.com (8.8.8/8.8.8) with SMTP id LAA00563; Wed, 18 Mar 1998 11:36:23 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: ppp6529.on.bellglobal.com: tim owned process doing -bs Date: Wed, 18 Mar 1998 11:36:22 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: "Steven G. Kargl" cc: freebsd-ports@FreeBSD.ORG Subject: Re: bsd.port.mk bug??? In-Reply-To: <199803181607.IAA05999@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Mar 1998, Steven G. Kargl wrote: > Seems that the mere presence of tk.h or tck.h in /usr/local/include > will stop the building of ALL ports unless I follow the instructions > to remove these files. This is rather draconian especially when the > most ports do not use tk/tcl. Think of it as a proactive bug. :-) If you really must, you can define NO_IGNORE (or something like that) to get past the check... -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message