Date: Mon, 24 Feb 2003 07:36:50 -0500 From: "Paul A. Howes" <pahowes@fair-ware.com> To: <freebsd-current@FreeBSD.ORG> Cc: "'leafy'" <leafy@leafy.idv.tw> Subject: RE: cc: Internal error: Illegal instruction (program as) Message-ID: <003e01c2dc01$68b47490$0200a8c0@howesnet> In-Reply-To: <20030224120738.GA1638@leafy.idv.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Jiawei,
I always remove the contents of /usr/obj prior to performing a
buildworld, and I could reproduce this behavior every time.
--
Paul A. Howes
-----Original Message-----
From: owner-freebsd-current@FreeBSD.ORG
[mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of leafy
Sent: Monday, February 24, 2003 7:08 AM
To: freebsd-current@fair-ware.com; freebsd-current@FreeBSD.ORG
Subject: Re: cc: Internal error: Illegal instruction (program as)
On Mon, Feb 24, 2003 at 12:10:46PM +0100, Soeren Schmidt wrote:
> > inverse provided in the kernel configuration file (ENABLE_PSE &
> > ENABLE_PG_G).
>=20
> Just for the record but my P4@2400/533 512MB/DDR does *not* show this=20
> problem no matter how hard I beat it.
>=20
> -S=FA=86en
Try this:
DON'T remove /usr/obj before doing a buildworld, just let it accumulate.
It will show up someday (it's not deterministic). Even sh(1) can die
during the build along with make(1) and as and gcc. My P4 never showed
such behaviour if I properly remove /usr/obj before a build.=20
Jiawei Ye=20
=20
--=20
"Without the userland, the kernel is useless."
--inspired by The Tao of
Programming
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003e01c2dc01$68b47490$0200a8c0>