Date: Mon, 21 Jun 2004 23:37:01 -0400 From: Damian Gerow <dgerow@afflictions.org> To: freebsd-current@freebsd.org Subject: Re: current build broken in another spot Message-ID: <20040622033701.GB85388@afflictions.org> In-Reply-To: <20040622033307.1CE4043D46@mx1.FreeBSD.org> References: <20040622033307.1CE4043D46@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Grover Lines (grover@ceribus.net) [21/06/04 23:34]: <snip> : -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bin : utils : -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bfd : -I/usr/obj/usr/src/i386/legacy/usr/include -c arparse.c : cccc: in free(): error: junk pointer, too high to make sense : Abort trap (core dumped) : *** Error code 134 See a post earlier today from David -- binutils should have been disconnected from the build. i.e. AFAIK, you shouldn't even be seeing this. Try re-sup'ing, and building again. (Is this even related to binutils, or is it an internal error?) The ipf breakage, however, /will/ stop your build. If you use ipf. - Damian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040622033701.GB85388>