From owner-freebsd-alpha Wed Jul 8 16:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15260 for freebsd-alpha-outgoing; Wed, 8 Jul 1998 16:24:31 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15245 for ; Wed, 8 Jul 1998 16:24:28 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA24415; Thu, 9 Jul 1998 09:38:04 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807082338.JAA24415@cimlogic.com.au> Subject: Re: ELF and Alpha conflict (lib/libc/nlist.c) In-Reply-To: <199807082215.RAA26145@bambi.visi.com> from "Brent J. Nordquist" at "Jul 8, 98 05:15:35 pm" To: bjn@visi.com Date: Thu, 9 Jul 1998 09:38:04 +1000 (EST) Cc: freebsd-alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brent J. Nordquist wrote: > My bootstrap buildworld stopped in lib/libc/nlist.c, throughout > which Elf32_* structs are sprinkled liberally. I hacked around it by > #define'ing them to their Elf64_* equivalents in sys/alpha/elf.h (ick). > > Has anyone raised this issue with the ELFmeisters? It seems like all > code should use something like Elf_* structs that are mapped to Elf32_* > or Elf64_* depending on platform. I have a version with the 64 bit code in the same style as the rest of the file. I haven't committed this because I don't think it is a clean solution. NetBSD has a far cleaner way of dealing with the similarities or 32 and 64 bit elf without duplicating code. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message