Date: Wed, 21 Aug 2002 22:26:37 +0200 From: Mark Santcroos <marks@ripe.net> To: KT Sin <ktsin@acm.org> Cc: Martin Blapp <mb@imp.ch>, freebsd-current@FreeBSD.ORG Subject: Re: Solved: CURRENT and P-IV problems Message-ID: <20020821202637.GG1348@laptop.6bone.nl> In-Reply-To: <20020821180517.GF1348@laptop.6bone.nl> References: <20020821152306.GE1348@laptop.6bone.nl> <20020821172613.L34509-100000@levais.imp.ch> <20020821153820.GA12394@sarang.Singapore.Sun.COM> <20020821180517.GF1348@laptop.6bone.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: > On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: > > Hi > > > > I believe this is caused by the pre-released version of gcc in the system. > > > > I started seeing this problem one week after I upgraded my hardware to > > Pentium 4 in May. Two weeks ago, I built the final release version of > > gcc 3.1.1 in the ports and used that to compile the kernel and userlands. > > > > All the strange signals have disappeared since then. > > Thanks for the hint, I'm building /usr/ports/lang/gcc31/ now. /usr/local/bin/gcc31 -fpic -DPIC -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/s_nextafter.c -o s_nextafter.So Illegal instruction (core dumped) *** Error code 132 Stop in /usr/src. *** Error code 1 That didn't work. I will now try the other gcc's from ports. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM 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?20020821202637.GG1348>