Date: Thu, 4 Sep 2003 21:42:58 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Marius Strobl <marius@alchemy.franken.de> Subject: Re: Question about genassym, locore.s and 0-sized arrays (showstopper for an icc compiled kernel) Message-ID: <200309050142.h851gwRB025223@khavrinen.lcs.mit.edu> In-Reply-To: <20030905011902.GA955@athlon.pn.xcllnt.net> References: <20030904180448.021a1b6b.Alexander@Leidinger.net> <20030904162858.GI98381@dan.emsphone.com> <20030905001411.3a9030b3.Alexander@Leidinger.net> <20030904224709.GA48780@ns1.xcllnt.net> <20030905025922.A68885@newtrinity.zeist.de> <20030905011902.GA955@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 4 Sep 2003 18:19:02 -0700, Marcel Moolenaar <marcel@xcllnt.net> said: > In theory, yes. In practice, maybe not. If I remember correctly, > the problem we're trying to solve is twofold: Actually, the problem we were trying to solve is simpler than that. genassym needs to be able to compute the values of certain constants from header files which are only accessible to kernel code. At the same time, it needs to be able to run as a user process. One compilation unit cannot include both Standard headers like <stdio.h> and kernel-specific headers like <sys/systm.h>. In fact, we muck with the include path to ensure that Standard headers cannot be included while compiling kernel source. Cross-compilation does engender other issues, but that wasn't the original motivation. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309050142.h851gwRB025223>