From owner-freebsd-hackers  Sun Apr  7 17:41:08 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA14543
          for hackers-outgoing; Sun, 7 Apr 1996 17:41:08 -0700 (PDT)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14538
          for <hackers@FreeBSD.org>; Sun, 7 Apr 1996 17:41:05 -0700 (PDT)
Received: from Early-Bird-1.Think.COM by mail.think.com; Sun, 7 Apr 96 20:40:56 -0400
Received: from compound.think.com ([206.10.99.158]) by Early-Bird.Think.COM; Sun, 7 Apr 96 20:40:52 EDT
Received: (from alk@localhost) by compound.think.com (8.7.5/8.6.112) id TAA10220; Sun, 7 Apr 1996 19:41:01 -0500 (CDT)
Date: Sun, 7 Apr 1996 19:41:01 -0500 (CDT)
Message-Id: <199604080041.TAA10220@compound.think.com>
From: Tony Kimball <alk@Think.COM>
To: dob@nasvr1.cb.att.com
Cc: hackers@FreeBSD.org
Subject: Re: pgcc and kernels
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


   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.

   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.

//alk