From owner-freebsd-hackers Sun Apr 7 18:15:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA16061 for hackers-outgoing; Sun, 7 Apr 1996 18:15:09 -0700 (PDT) Received: from gw3.att.com ([204.179.186.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA16055 for ; Sun, 7 Apr 1996 18:15:07 -0700 (PDT) From: dob@nasvr1.cb.att.com Received: from nasvr1.cb.att.com (naserver1.cb.att.com) by ig4.att.att.com id AA15800; Sun, 7 Apr 96 21:07:02 EDT Received: by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2) id AA08960; Sun, 7 Apr 1996 21:15:17 -0400 Received: from cbsky.cb.att.com by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2) id AA08951; Sun, 7 Apr 1996 21:15:14 -0400 Received: by cbsky.cb.att.com (5.x/EMS-1.1 client.cf 1/8/94 (SMI-4.1/SVR4)) id AA12449; Sun, 7 Apr 1996 21:14:46 -0400 Date: Sun, 7 Apr 1996 21:14:46 -0400 Message-Id: <9604080114.AA12449@cbsky.cb.att.com> To: alk@Think.COM Cc: hackers@FreeBSD.org Subject: Re: pgcc and kernels Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > From Think.COM!alk@ig4.att.att.com Sun Apr 7 20:41 EDT 1996 > From: Tony Kimball > > Didn't readily find the source for muldi3.c > ... > Kernel compiles and links ok but the resulting kernel panics out of > _scsi_attach during probe phase. > > In your sys directory, unless I'm not uttering a tautology, there is a libkern/muldi3.c. > I haven't checked for differences from the pgcc supplied run-time, so > I suggest checking for differences. If it panics anywhere in > vfs_bio.c, vfs_cluster.c, subr_prof.c, or kern_resource.c, I'd say it > is dollars to donuts that your _muldi3.c from the pgcc distribution is > NOT acceptable -- use the libkern one instead, for it works for me. Thanks. Found it. Made it (per Jordan's suggestion ala Makefile). Didn't work. Panic'ed like before (trace): _scsi_attachdevs + x20 _ncr_attach + x199 _pci_bus_config + x4e8 _pci_configure + x4f _configure + x21 _main + xx87 begin + x59 Something else is non-copastetic. > This didn't work for me. Couldn't find kcc, so I just gave it CC=cc. > > Right, whatever, mutatis mutandis, check, okay, cool: > Me, I replaced cc/gcc with pgcc, leaving only kcc as a fall-back. Huh, I get it now... Pardon my naivete' :-) Peace, Dan