From owner-freebsd-ports Sun Sep 10 01:18:08 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA28943 for ports-outgoing; Sun, 10 Sep 1995 01:18:08 -0700 Received: from condor.physics.montana.edu (condor.physics.montana.edu [153.90.240.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA28933 for ; Sun, 10 Sep 1995 01:18:06 -0700 Received: (from handy@localhost) by condor.physics.montana.edu (8.6.11/8.6.9) id CAA09856; Sun, 10 Sep 1995 02:17:34 -0600 Date: Sun, 10 Sep 1995 02:17:34 -0600 (MDT) From: Brian Handy To: freebsd-ports@freebsd.org Subject: Possible broken ports? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@freebsd.org Precedence: bulk I just built a stock 2.1.0-950726-SNAP system on a Pentium, rebuilt the kernel to cut out all the junk and started throwing ports all over the place. I had a couple that didn't make it: (1) perl5: configures great, but falls over with: [...] Extracting x2p/s2p (with variable substitutions) Run make depend now? [y] "Makefile", line 110: Need an operator "Makefile", line 233: Need an operator Fatal errors encountered -- cannot continue ===> Building for perl-5.001 "Makefile", line 110: Need an operator "Makefile", line 233: Need an operator Fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 Stop. (2) xcdplayer: compiles fine, but when I started actually using it (I have a "FUJITSU M1606S-512 6226" on a AHA-2940 scsi bus), it managed to completely lock up my system. My gauge of a locked up system is when things are so bad the numlock key doesn't light up anymore...and I was there. Whole system locked up waiting for something to happen. It occured when I was punching buttons wildly trying to figure out what everything did. This is all I've got so far. I'm not in the ports group, please keep me in the :cc (especially in case I've done something dumb.) Thanks Brian