From owner-freebsd-alpha@FreeBSD.ORG Thu Mar 27 06:02:46 2003 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FBDD37B401 for ; Thu, 27 Mar 2003 06:02:46 -0800 (PST) Received: from arthur.vortex4.net (arthur.vortex4.net [216.27.179.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 8988243F93 for ; Thu, 27 Mar 2003 06:02:45 -0800 (PST) (envelope-from friend@vortex4.net) Received: (qmail 61790 invoked by uid 1000); 27 Mar 2003 14:02:45 -0000 Date: Thu, 27 Mar 2003 06:02:44 -0800 From: Dave To: freebsd-alpha@freebsd.org Message-ID: <20030327060244.I46996@vortex4.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD arthur.vortex4.net 4.8-RC FreeBSD 4.8-RC X-System-Stats: 2:33PM up 2 days, 20:18, 2 users, load averages: 0.00, 0.00, 0.00 X-Spam-Status: No, hits=-6.4 required=5.0 tests=USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: -march=pca56 blows up nethack34 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2003 14:02:47 -0000 Hey all, I'm not sure if there's a more appropriate forum to report this problem, and any relevent feedback on that front would be appropriate. I recently installed 5.0-RELEASE on a PC164SX Alpha system, dutifully set my CPUTYPE to pca56 in /etc/make.conf, built & installed world without problems, and started adding important ports to the system, most notably nethack34-nox11. I found after building it (with no reported problems), that it wouldn't run-- after the class/race/alignment selection (or lackthereof if you let it select for you), the game would bomb out with "illegal instruction". I solved the problem by pkg_delete'ing the port, commenting out the CPUTYPE var from /etc/make.conf, and rebuilding it. Now it works with no problems. So I'm wondering a couple of things. First, has anyone seen anything like this before with other ports on 5.x for alpha? Is it "safe" to specify my CPUTYPE? Second, who would benefit the most from this bug report? The alpha list? the current list? the port maintainer? Feedback is appreciated. Thanks! -- Dave Cotton friend@vortex4.net