Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Apr 1996 21:14:46 -0400
From:      dob@nasvr1.cb.att.com
To:        alk@Think.COM
Cc:        hackers@FreeBSD.org
Subject:   Re: pgcc and kernels
Message-ID:  <9604080114.AA12449@cbsky.cb.att.com>

next in thread | raw e-mail | index | archive | help
> From Think.COM!alk@ig4.att.att.com Sun Apr  7 20:41 EDT 1996
> From: Tony Kimball <alk@Think.COM>
> 
>    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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9604080114.AA12449>