Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: Problems with new patches espec. patch00089 Message-ID: <1993Mar8.211046.2540@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS References: <sturges-030393120454@humble.lds-az.loral.com> <C3Kquz.Bxv@cosy.sbg.ac.at> Date: Mon, 8 Mar 1993 21:10:46 GMT Lines: 42 In article <C3Kquz.Bxv@cosy.sbg.ac.at> peter@cosy.sbg.ac.at writes: > >Hi folks! >I just installed the new patches 84-110. >I ran into several problems. >1. config did core dump because of the "#" in several files like > file.i386, devices ... >I deleted all comments and config worked again. > Not good. You need to re-compile config, that is why there are patches to it. >2. Either I did miss something or there is a bug in patch00089. > I tried to recompile libc (atof.c was changed by this patch) > and got the following output: >/usr/src/lib/libc/i386/stdlib/atof.c: In function strtod: >/usr/src/lib/libc/i386/stdlib/atof.c:156: warning: assignment of non-const * pointer >from const * >cc: Program cc1 got fatal signal 6. >*** Error code 1 You ran into the same problem I did. cd /usr/src/include make install And try again. It should work now. >Do I have to recompile something before getting rid of the signal 6 error >or is there a bug in atof.c ?? You have to recompile EVERYTHING that has changed when you apply the patchkit. The current patchkit doesn't make that obvious, but it still needs to be done. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom