From owner-freebsd-alpha Mon Nov 11 7:18:45 2002 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 5B4A037B401 for ; Mon, 11 Nov 2002 07:18:44 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A606343E75 for ; Mon, 11 Nov 2002 07:18:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA06090; Mon, 11 Nov 2002 10:18:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABFIDA47946; Mon, 11 Nov 2002 10:18:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.51765.171947.796322@grasshopper.cs.duke.edu> Date: Mon, 11 Nov 2002 10:18:13 -0500 (EST) To: Poul-Henning Kamp Cc: alpha@FreeBSD.ORG Subject: Re: ev4/5/6 issue ? In-Reply-To: <55220.1037026411@critter.freebsd.dk> References: <15823.49990.899445.424699@grasshopper.cs.duke.edu> <55220.1037026411@critter.freebsd.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul-Henning Kamp writes: > 12001f4e4: 82 04 1f 52 itoft a0,$f2 OK, this is a FIX instruction, which is not implemented on ev4, nor even ev5 or ev56. We also don't bother to emulate it in the kernel, since no commercial binaries depend on it. Your initial assertion that this might be happening because the libraries are built for ev6 on beast could be true. Can you verify that that 12001f4e4 is indeed inside a library function using nm? (12001f4e4 is looks like a library address, but it would be better to be certain). If so, perhaps you could link make shared on beast and get yourself bootstrapped that way. That doesn't solve the initial problem of why your make was busted, though. If its in the libs, then your libs are likely busted too. Perhaps you'll also need to build a libc on beast, explicitly setting your cpuflags to ev4. Or perhaps the compiler is emitting FIX instructions when it should not. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message