Date: Sat, 24 Jan 2004 11:45:30 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: erek <erek@necrotec.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5.2-RELEASE buildworld failure. Message-ID: <20040124094530.GH51326@FreeBSD.org.ua> In-Reply-To: <49178.216.9.170.168.1074910404.spork@webmail.necrotec.com> References: <49178.216.9.170.168.1074910404.spork@webmail.necrotec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--QDIl5R72YNOeCxaP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 p= oisoned "malloc" [...] > mkdep: compile failed > *** Error code 1 [...] > any suggestions? >=20 <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 =66rom 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: :=20 : In file included from /usr/src/contrib/binutils/bfd/targets.c:109= 2: : targmatch.h:7:1: null character(s) ignored : targmatch.h:12:1: null character(s) ignored : targmatch.h:16:1: null character(s) ignored : : :=20 : 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, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --QDIl5R72YNOeCxaP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAEj66Ukv4P6juNwoRAoFrAJ4pIVaAFxR8soihm01vXlBoi4jLBgCeNDJu 08JCoIroJxfceH1ab6uemGs= =p94o -----END PGP SIGNATURE----- --QDIl5R72YNOeCxaP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040124094530.GH51326>