From owner-freebsd-current Tue Apr 4 17:14:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA27154 for current-outgoing; Tue, 4 Apr 1995 17:14:51 -0700 Received: from mail.barrnet.net (mail.BARRNET.NET [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA27148 for ; Tue, 4 Apr 1995 17:14:49 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id RAA20540 for ; Tue, 4 Apr 1995 17:11:54 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Tue, 4 Apr 1995 19:14:11 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Apr 1995 19:14:14 -0500 To: current@FreeBSD.org, rgrimes@gndrsh.aac.dev.com, nate@trout.sri.MT.net From: rkw@dataplex.net (Richard Wackerbarth) Subject: Genassym Sender: current-owner@FreeBSD.org Precedence: bulk OK! I have an "out" that I think might satisfy all of our demands. 1) ALWAYS force genassym to reference /usr/include for its library headers. 2) NEVER include the objects or binaries of any of the kernel or kernel specific tools in any distribution. REQUIRE that they be recompiled when used on any machine. After all, as Nate points out, genassym is a "tool" to be executed on the host machine and not something that runs on the target. I haven't looked at genassym, but assume that it uses the sys headers only as input text, or equivalently, conditional conpilation flags. If it makes any assumptions about kernel data structures, etc. it will eventually break in cross platform compilation. :( -- OR -- Allow me to specify a correct cross-compilation environment and move genassym to the "tools" portion of that structure. In that case, the correct files will be automatically referenced. ---- Richard Wackerbarth rkw@dataplex.net