On Fri, Jan 23, 2004 at 06:13:24PM -0800, erek wrote:
> I cvsuped today using tag RELENG_5_2 (i'm already using 5.2-RELEASE),
[...]
> During the buildworld I get this VERY odd error:
[...]
> /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use poisoned 
> "malloc"
[...]
> mkdep: compile failed
> *** Error code 1
[...]
> any suggestions?
> 
<wizard mode>

Go to /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus, and compare
parse.c and parse+%DIKED.c there.  They should be different, "xmalloc"
vs "malloc", "xrealloc" vs "realloc.  If they are identical, chances
are your /usr/bin/sed is probably broken, and you should read this entry
from src/UPDATING:

: 20030613: [retrospective]
:         There was a small window in which sed(1) was broken.  If you
:         happen to have sed(1) installed during that window, which is
:         evidenced by an inability to build world with the failure
:         given below, you need to manually build and install sed(1)
:         (and only sed(1)) before doing anything else. This is a one-
:         time snafu. Typical failure mode:
: 
:         In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
:         targmatch.h:7:1: null character(s) ignored
:         targmatch.h:12:1: null character(s) ignored
:         targmatch.h:16:1: null character(s) ignored
:                 :
: 
:         The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
:         to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
:         usr.bin/sed/process.c).

To see if you're affected, run this:

ident /usr/bin/sed

And see which process.c revision your sed(1) has.  It if's 1.30,
you're affected.

</wizard mode>


Cheers,
-- 
Ruslan Ermilov
FreeBSD committer
[EMAIL PROTECTED]

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to