From owner-freebsd-current@FreeBSD.ORG Sat Jul 26 04:02:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 986AB37B401 for ; Sat, 26 Jul 2003 04:02:17 -0700 (PDT) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FFCA43FB1 for ; Sat, 26 Jul 2003 04:02:16 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.9/8.12.9) with ESMTP id h6QB3mvo029150; Sat, 26 Jul 2003 13:03:50 +0200 (CEST) From: Thierry Herbelot To: John , Current List Date: Sat, 26 Jul 2003 13:01:53 +0200 User-Agent: KMail/1.5.2 References: <20030725224650.GA20382@BSDWins.Com> In-Reply-To: <20030725224650.GA20382@BSDWins.Com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200307261301.54001.thierry@herbelot.com> Subject: Re: gcc related -current upgrade problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 11:02:17 -0000 Le Saturday 26 July 2003 00:46, John a écrit : > . > /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use > poisoned "malloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:63:25: > attempt to use poisoned "calloc" > /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:64:25: attempt to use > poisoned "realloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:65:25: > attempt to use poisoned "strdup" mkdep: compile failed Hello, I've seen yesterday the exact same error : (maybe some bad wave coming to us from the outer space ?) one one machine (A). What was surprising in my case was that this error was systematic : I've tried three compilations in a succession to be sure it was not an error due to bad hardware. Then I've transferred the hard disk to another machine (B), and relaunched the "make buildworld" to check that the compiler and the sources on the disk were good (and indeed the make buildworld an make buildkernel succeeded on machine B) then I've re-transferred back the disk to the first machine, and I could then "make buildworld" - big surprise ? the first machine uses a Pentium-4 mobile (a real P-IV, not a Banias) and the second machine uses a Pentium-III TfH