Date: Fri, 6 Dec 2002 14:11:26 -0800 From: Kent Stewart <kstewart@owt.com> To: John Mills <john.m.mills@alum.mit.edu>, John Mills <jmmills@telocity.com> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: buildworld fail Message-ID: <200212061411.26848.kstewart@owt.com> In-Reply-To: <Pine.LNX.4.21.0212061702330.1246-100000@otter.mills-atl.com> References: <Pine.LNX.4.21.0212061702330.1246-100000@otter.mills-atl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 06 December 2002 02:03 pm, John Mills wrote: > Kent - > > On Fri, 6 Dec 2002, Kent Stewart wrote: > > On Friday 06 December 2002 01:38 pm, Steve Bertrand wrote: > > > Kent: > > > > > > I see the differences between the compiler commands, but have > > > no idea how to change them. I would like to try your idea. I > > > have given no special flags to make. What flags would I give > > > to make when making world? > > > > #CFLAGS=3D -O -pipe > > #COPTFLAGS=3D -O -pipe > > > > These are the defaults and so I just commented them out in > > /etc/make.conf. > > > > I would assume you have something defining a cpu or a CFLAGS. I > > don't use either. I have a mix of cpus and have had to NFS mount > > /usr/src and /usr/obj to recover a system before. I don't use cpu > > or compiler options. > > Maybe that will get me through the build, too. I'll certainly give > it a shot. Just remember that a signal 11 in a compile is usually your hardware=20 telling you something is wrong. If it dies at the same spot, it can=20 be options or whatever. If you use strange options, you have to try=20 them first but still remember a signal 11is normally related to=20 memory or heating problems. Kent --=20 Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212061411.26848.kstewart>