RE: current build broken in another spot

I just cvsupd like 5 minutes ago. I'll give it another shot though

 Grover Lines

> -----Original Message-----
> From: owner-freebsd-current_at_freebsd.org [mailto:owner-freebsd-
> current_at_freebsd.org] On Behalf Of Damian Gerow
> Sent: Monday, June 21, 2004 8:37 PM
> To: freebsd-current_at_freebsd.org
> Subject: Re: current build broken in another spot
> 
> Thus spake Grover Lines (grover_at_ceribus.net) [21/06/04 23:34]:
> <snip>
> : -
> I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bi
> n
> : utils
> : -
> I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bf
> d
> : -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
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"