Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:10629 comp.os.386bsd.apps:1292 comp.os.386bsd.questions:11677 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!ames!hookup!swrinde!howland.reston.ans.net!math.ohio-state.edu!sdd.hp.com!saimiri.primate.wisc.edu!black-hole From: dubois@primate.wisc.edu (Paul DuBois) Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.apps,comp.os.386bsd.questions Subject: Re: __NetBSD__ X11R6 i386 Date: 19 Jul 1994 12:51:56 -0500 Organization: Castra Parvulorum Lines: 17 Sender: dubois@uakari.primate.wisc.edu Message-ID: <30h3rtINN1q9@uakari.primate.wisc.edu> References: <30dr4j$phk@darum.uni-mannheim.de> Reply-To: dubois@primate.wisc.edu NNTP-Posting-Host: uakari.primate.wisc.edu > Has anybody been successful with getting X11R6 running under NetBSD ? > ... > Also the CppSedMagic doesn't seem to be called up for the makefiles > thus XCOMM is put in the Makefile multiple times. CppSedMagic isn't involved in creating the Makefiles; it's for creating other scripts from templates that get run through cpp. But the symptom of XCOMM appearing in your Makefile suggests that the R6 imake might not be getting invoked correctly. XCOMM in Makefiles is exactly what happens when you use R6 configuration files with R5 (or earlier) imake. So you might check that. -- Paul DuBois dubois@primate.wisc.edu