From owner-freebsd-questions Mon Jun 21 8:13:37 1999 Delivered-To: freebsd-questions@freebsd.org Received: from tad.cetlink.net (tad.cetlink.net [209.198.2.10]) by hub.freebsd.org (Postfix) with ESMTP id AA3EE14CFD; Mon, 21 Jun 1999 08:13:31 -0700 (PDT) (envelope-from jeff@tad.cetlink.net) Received: (from jeff@localhost) by tad.cetlink.net (8.9.2/8.9.1) id LAA93060; Mon, 21 Jun 1999 11:13:31 -0400 (EDT) (envelope-from jeff) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 21 Jun 1999 11:13:31 -0400 (EDT) Organization: CETLink.Net From: Jeff Wheat To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Alpha port Questions Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good day everyone, I have a few questions regarding FreeBSD-3.2 for the alpha platform. I have the system installed and running just fine. My problem however is with the ports collections. I am running FreeBSD on a Dec AlphaStation 250 4/266. When I attempt to build most things in the ports collection by typing "make" in a port directory, configure will do something to the tune of "alpha--FreeBSD" when configure tries to guess the system type. Going directly into the port work directory and running configure by hand usually will return "alpha-unknown-FreeBSD". The TCSH port and package both return the following: alpha # set version tcsh 6.08.00 (Astron) 1998-10-02 (i386-unknown-FreeBSD) options 8b,nls,d l,al,sm,rh,color alpha# file /usr/local/bin/tcsh /usr/local/bin/tcsh: ELF 64-bit LSB executable, Alpha, version 1 (FreeBSD), stri pped This is of course very wrong... Are there any fixes or work arounds for this? Many thanks in advance... Please reply directly to me as I am not yet subscribed to any of these lists. Best regards, Jeff --------------End of forwarded message------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message