Date: Tue, 28 Jan 2003 17:42:59 -0800 From: Juli Mallett <jmallett@FreeBSD.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: current@FreeBSD.ORG Subject: Re: Patch to teach config(8) about "platforms". Message-ID: <20030128174259.A10304@FreeBSD.org> In-Reply-To: <20030129013537.GB1016@athlon.pn.xcllnt.net>; from marcel@xcllnt.net on Tue, Jan 28, 2003 at 05:35:37PM -0800 References: <20030125153116.A25743@FreeBSD.org> <20030128.233856.71130419.nyan@jp.FreeBSD.org> <20030128120830.A81856@FreeBSD.org> <20030128225335.GB537@athlon.pn.xcllnt.net> <20030128151749.A831@FreeBSD.org> <20030128235528.GA844@athlon.pn.xcllnt.net> <20030128160936.A4252@FreeBSD.org> <20030129004006.GA945@athlon.pn.xcllnt.net> <20030128164955.A7369@FreeBSD.org> <20030129013537.GB1016@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Marcel Moolenaar <marcel@xcllnt.net> [ Data: 2003-01-28 ] [ Subjecte: Re: Patch to teach config(8) about "platforms". ] > On Tue, Jan 28, 2003 at 04:49:55PM -0800, Juli Mallett wrote: > > > > > So, given that we have MACHINE_ARCH and MACHINE already to our > > > disposal, I don't get the feeling that we are in need to add > > > something else because the problem space appears 2D, not 3D. > > > > > > Right? > > > > That's what I'm trying to do, in a clean way. See my "short version" > > message, if you like. > > Ok. Now that we've established that the "platform" keyword is not > needed, is there any meaning we attach to MACHINE that conflicts > with the meaning it must have in order to solve the mips/powerpc > problem? Or do we not attach a certain meaning to MACHINE that we > should attach to it? No, we have not established that. Using machine still does not fix the <machine> issues. If we keep everything under "mips" for the mchine architecture (/sys/mips) then we need platform to get stuff from the per-$MACHINE directories in a generic way, or every $MACHINE needs to be known to the upper-level, exposing implementation details along the lines of every <machine> header (those are under MACHINE_ARCH _not_ MACHINE's domain, given how config works). If we keep all the meta- ports under /sys/mips then <machine> is /sys/mips/include, NOT e.g. /sys/mips/sgimips or /sys/mips/sgimips/include with a "machine sgimips" and neither is an option set to turn on optional SGIMIPS hardware. The machine keyword has NOTHING to do with the <machine> directory, except in the case where /sys/$MACHINE/compile/$KERNCONF is where the port ends up being built, and where the "machine" setting is equal to $MACHINE above. Such as pc98. I'm not talking about how pc98 works, with platform. That way is dumb and braindead and does not work. As Benno said, platform is for per-platform quirks. We attach lots of meaning to MACHINE. You keep missing that that is NOT the same as the "machine" keyword. It is, however, the same as the "platform" keyword. Thanx, juli. -- Juli Mallett <jmallett@FreeBSD.org> AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030128174259.A10304>