From owner-freebsd-questions Tue Feb 8 6:46:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from goof.com (goof.com [12.4.218.41]) by builder.freebsd.org (Postfix) with SMTP id B14DD4231 for ; Tue, 8 Feb 2000 06:46:33 -0800 (PST) Received: (qmail 23135 invoked by uid 15016); 8 Feb 2000 14:47:25 -0000 Date: Tue, 8 Feb 2000 09:47:25 -0500 From: Jon-Erik Lido To: freebsd-questions@freebsd.org Subject: Re: Broken ports collection Message-ID: <20000208094725.A22592@goof.com> Mail-Followup-To: freebsd-questions@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Mike Morgan on Thu, Feb 03, 2000 at 07:18:02PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey everyone, I'm still having problems using the Ports Collection. To summarize the problem, I'm getting errors every time I try to run "make" on a port. Ports used to be my favorite feature of FreeBSD, but they haven't worked since I installed 3.4 Release (on a clean machine). What I see when I try to make a port is errors like: "/usr/ports/Mk/bsd.port.mk", line 649: warning: String comparison operator should be either == or != "/usr/ports/Mk/bsd.port.mk", line 649: Malformed conditional (defined(USE_NEWGCC) && ${OSVERSION} < 400012) So far it's been suggested that I'm using gmake instead of BSD's make, but I've verified that is not the case. It was also suggested that I cvsup the ports collection. I have tried that, but I'm getting the same problem with the latest and greatest ports. It seems clear to me a this point that the problem is not with the ports collection itself, but with some other problem with my machine's configuration. It should be noted that I can compile kernels and other programs (for instance ssh) just fine using make. Basically, I don't know what else to check. The ports files themselves seem fine. make seems fine. cc seems fine. What next? I'm baffled! Thanks, -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message