On Wed, Jan 29, 2003 at 12:55:30PM -0800, Juli Mallett wrote: > * De: Marcel Moolenaar <[EMAIL PROTECTED]> [ Data: 2003-01-29 ] > [ Subjecte: Re: Patch to teach config(8) about "platforms". ] > > > If we just make "machine" mean more of what it means now, then we're > > > set. > > > > But pc98 needs to be dealt with. Maybe a summary of what's been > > discussed would be a good idea. We've had a lot of mail with some > > confusion to be dealt with as well... > > Well, yes and no... If we make machine mean more of "where stuff is" > which is what it means now, then we can have "machine pc98" for it, > until it moves to the "new world order" (if ever) and use that to figure > out where files,options,ldscript,... And so on, fine. It obviously already > does the right thing wrt MACHINE_ARCH for how things work. Those are > defined by the native system's headers when make is built. And for a > cross-build, they're overridden. So if we just add that one tiny little > bit of logic to end up with /sys/$machine (for config), then pc98 is > fine even wrt being able to build outside of the source tree... Can you > tell me where pc98 is a problem here?
I thought the idea was to have machine be usable for platforms, so as to have the mapping machine->MACHINE. This makes the keyword unusable for handling the pc98 case. I guess I was confused (now you know who needs the summary :-) -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
