Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Jul 2003 13:01:53 +0200
From:      Thierry Herbelot <thierry@herbelot.com>
To:        John <jwd@bsdwins.com>, Current List <freebsd-current@freebsd.org>
Subject:   Re: gcc related -current upgrade problems
Message-ID:  <200307261301.54001.thierry@herbelot.com>
In-Reply-To: <20030725224650.GA20382@BSDWins.Com>
References:  <20030725224650.GA20382@BSDWins.Com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307261301.54001.thierry>