From owner-freebsd-current Fri Sep 11 00:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28534 for freebsd-current-outgoing; Fri, 11 Sep 1998 00:49:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28529 for ; Fri, 11 Sep 1998 00:49:36 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA01964; Fri, 11 Sep 1998 17:49:20 +1000 Date: Fri, 11 Sep 1998 17:49:20 +1000 From: Bruce Evans Message-Id: <199809110749.RAA01964@godzilla.zeta.org.au> To: jb@cimlogic.com.au, street@iName.com Subject: Re: kernel build error under ELF Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yes, I've seen a report of this. The suggestion was to build genassym >with the installed object format. To do this the flags need to be >set so that they don't contain the -aout argument. It will be 24 hrs >before I can spend any time on this. genassym (and linux_genassym) should be built by the target compiler (target = system that will run the kernel) yet must run on the host system and use the host stdio. This is impossible in general. The "compiler" should somehow be switched after compiling to assembler or object code. E.g., perhaps everything can be encoded into stabs which can easily be interpreted after printing them using nm -a. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message