From owner-freebsd-questions Fri Mar 29 8:10:49 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.nortenet.pt (mar.nortenet.pt [212.13.32.243]) by hub.freebsd.org (Postfix) with ESMTP id 8A85B37B404 for ; Fri, 29 Mar 2002 08:10:37 -0800 (PST) Received: from nortenet.pt (v1-pppS54.nortenet.pt [212.13.32.54]) by mail.nortenet.pt (8.11.1/8.11.1) with ESMTP id g2TF7ih18919; Fri, 29 Mar 2002 16:07:45 +0100 Message-ID: <3CA493A4.BF7265B3@nortenet.pt> Date: Fri, 29 Mar 2002 16:17:40 +0000 From: Guilherme Oliveira Organization: Host-Valley.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586) X-Accept-Language: pt, pt-BR, en MIME-Version: 1.0 To: Jens Rehsack Cc: Doug Reynolds , "freebsd-questions@freebsd.org" Subject: Re: Bug ? Building kernel/world error on Cyrix [resolved] References: <20020329044358.BD7654844F@wastegate.net> <3CA3F3A4.493DAD69@nortenet.pt> <3CA45790.6A5AC345@liwing.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jens Rehsack wrote: > > If I run into a problem like this, > 1st: I look for a core dump. If there is a one, I look for the last executed > command (in your case it seems to be perl), so I run > bash-2.05a# gdb perl core > (gdb) bt > .... > now you see where the error is. This is a good help, but I haven't begined to programm in UNIX yet. > > I got a problem earlier and a rebuild of world and make a "make install" > in /usr/src/contrib/perl/libperl (or so) removed the problem. It worked compiling code only with optimizations for i386. I think your suggestion might work too because I have builded and installed world+kernel just fine again with 'CPUTYPE=i686' in make.conf and 'cpu I686_CPU' in kernel configuration :// > 2nd: if nothing seems to help, I delete the entire /usr/src & /usr/obj, re-cvsup > and rebuild it all. Also check /etc/make.conf if you make sth. ... I did that already. I think that I need some option in kernel configuration file specific to this processor such as CPU_CYRIX_NO_LOCK or CPU_LOOP_EN because when building breaked in vnode (using i686 optimizations) the cpu was almost 100% ... Thanks for all ! -- mailto:guilherme@nortenet.pt || http://guilherme.host-valley.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message