Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5709 ; Fri, 01 Jan 93 01:53:21 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uunet!sparky!dsndata!dsndata!randy From: randy@dsndata.dsndata.com (Randy Terbush) Subject: Re: gcc-2.3.2 and kernel build In-Reply-To: mycroft@hal.gnu.ai.mit.edu's message of 28 Dec 92 16:37:54 GMT Message-ID: <RANDY.92Dec29130938@dsndata.dsndata.com> Sender: randy@dsndata.uucp (Randy Terbush) Organization: Design Data References: <RANDY.92Dec28095652@dsndata.dsndata.com> <1hnah2INNni9@life.ai.mit.edu> Date: Tue, 29 Dec 1992 19:09:43 GMT Lines: 27 >>>>> "Charles" == Charles Hannum <mycroft@hal.gnu.ai.mit.edu> writes: > I am tripping over many problems created by running fixincludes, and > using the resulting include files. What experiences are others > having? 'fixincludes' used gnu 'sed' on my system since I have > found some problems with the supplied 'sed'. Charles> The installation notes state that you should only run Charles> `fixincludes' if you don't already have ANSI-compliant Charles> include files. Doing compiles without the "fixed" include files produces many ANSI compliance errors. 'sed' failed to make proper changes in many files, and this is also causing problems. The 'fixincludes' script finds that MOST of the include files are NOT ANSI compliant. I am just beginning to discover what works and doesn't on 386bsd, and I may still be missing something. Any suggestions are appreciated. Randy Terbush ------------------------------------- Design Data, Inc. UUCP: netcomsv!dsndata!randy ---------------------- 1033 'O' st. Suite 324 INET: randyt@oto.unl.edu -------------------------- Lincoln, NE 68508 --------------------------------------------------- 402-476-8278