Date: Thu, 4 Oct 2007 15:54:06 -0400 From: Mikhail Teterin <mi+mill@aldan.algebra.com> To: Greg Lewis <glewis@eyesbeyond.com>, ache@freebsd.org, John Reynolds <johnjen@reynoldsnet.org> Cc: freebsd-java@freebsd.org Subject: status of gcc on -current (Re: status of FreeBSD port java/berkeley-db) Message-ID: <200710041554.06861.mi%2Bmill@aldan.algebra.com> In-Reply-To: <20071004192528.GA63715@misty.eyesbeyond.com> References: <20071004091427.GA89864@hub.freebsd.org> <200710041157.11201.mi%2Bmill@aldan.algebra.com> <20071004192528.GA63715@misty.eyesbeyond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
четвер 04 жовтень 2007 03:25 по, Greg Lewis Ви написали: > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007100120/je-3.2.13_1.log > Probably due to the gcc 4.2 problems on -current. It should go away when > the cluster picks up obrien@'s fix to turn of tree-vrp. Most interesting... I'm getting problem reports from people, who try to build ImageMagick on -current -- ImageMagick's self-tests report strange failures. But building with a port-built gcc 4.2 on -stable works fine, so either the port did not have the -current's bug in it, or it is something in addition to the compiler :( Thanks! -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710041554.06861.mi%2Bmill>