Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!rpi!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: Hmmm... Evil signal 6 again! Message-ID: <1993Mar8.174417.8320@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS References: <C3Gw2z.CIz@news.cso.uiuc.edu> <JKH.93Mar6214040@whisker.lotus.ie> Date: Mon, 8 Mar 1993 17:44:17 GMT Lines: 26 In article <JKH.93Mar6214040@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: > >In article <C3Gw2z.CIz@news.cso.uiuc.edu> rkb55989@uxa.cso.uiuc.edu (Rafal) writes: > I've now got Gcc2.3.3 happily compiled, and am attempting to compile > away all my utils, libs, so I can -m486 them, and because I also > installed the new patches (84-110). However, ldexp in LIBC still > bombs out on a signal 6... > >This is weird. It works for me and several other people I've asked, yet >I've seen this problem report twice now. Does anyone else see this? Duhh... I was seeing it, but that was because I forgot to do a make install in /usr/src/include. I had naively assumed that the changes were in /usr/include, but the patch went into the more correct /usr/src/include. After that, things work OK for me. Make sure you install the fixed include files. 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