Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!bin From: bin@primate.wisc.edu (Brain in Neutral) Newsgroups: comp.sys.mips Subject: Re: R4 server for RS1210 (aka NCD16)? Message-ID: <3210@uakari.primate.wisc.edu> Date: 2 Oct 90 18:32:20 GMT References: <41849@mips.mips.COM> Sender: bin@primate.wisc.edu Reply-To: bin@primate.wisc.edu Lines: 42 From article <41849@mips.mips.COM>, by rogerk@mips.COM (Roger B.A. Klorese): | In article <3204@uakari.primate.wisc.edu> bin@primate.wisc.edu writes: |>> #ifdef Mips |>> # define MacroIncludeFile "Mips.cf" |>> # define MacroFile Mips.cf |>> # undef Mips |>> # if defined(SYSTYPE_BSD) || defined(BSD) || defined(BSD43) |>> # define MipsBsdArchitecture |>> # else /* BSD */ |>> # define MipsSysvArchitecture |>> # endif /* BSD */ |>> #endif /* Mips */ |> |>Thanks. But... |>(1) I thought RISCOS was the unique symbol. The block is tested against |>the symbol "Mips". | | ....which is elsewhere defined in the Makefiles. This was a decision made | by the graphics SW group; OS uses RISCOS, and I don't think either is | likely to change in the near future. *Sigh* Mmm. Mips is defined in the Makefiles? But the Makefiles are generated from the Imakefiles and the templates, and the templates test against Mips. There is a problem here somewhere. >>(3) > # if defined(SYSTYPE_BSD) || defined(BSD) || defined(BSD43) >>Yow. Why is "#ifdef SYSTYPE_BSD" insufficient? > > I think the issue is that code which defines BSD or BSD43 should be > treated as if it were generated in -systype bsd43. I'm not sure this is > a correct assumption, though. It may be possible to get around it by making sure that imakemdep.h defines the correct symbols for ccimake/imake when imake is initially built. Then you could rely on a specific, single symbol in Imake.tmpl. But again, this depends on the contents of BOOTSTRAPCFLAGS being well-defined for the initial configuration. Chicken/egg? -- Paul DuBois dubois@primate.wisc.edu "Was all of this because I wore a big man's hat?"