From owner-cvs-ports@FreeBSD.ORG Tue Jul 20 05:51:35 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 413E016A4CE; Tue, 20 Jul 2004 05:51:35 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0037F43D45; Tue, 20 Jul 2004 05:51:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-64-169-104-4.dsl.lsan03.pacbell.net [64.169.104.4])i6K5pYAt027201; Tue, 20 Jul 2004 01:51:34 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DD80F51A1C; Mon, 19 Jul 2004 22:51:33 -0700 (PDT) Date: Mon, 19 Jul 2004 22:51:33 -0700 From: Kris Kennaway To: Dirk Meyer Message-ID: <20040720055133.GA68249@xor.obsecurity.org> References: <200407200541.i6K5fgNg080883@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <200407200541.i6K5fgNg080883@repoman.freebsd.org> User-Agent: Mutt/1.4.2.1i cc: cvs-ports@FreeBSD.org cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/net/vls Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 05:51:35 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 20, 2004 at 05:41:42AM +0000, Dirk Meyer wrote: > dinoex 2004-07-20 05:41:42 UTC >=20 > FreeBSD ports repository >=20 > Modified files: > net/vls Makefile=20 > Log: > - mark BROKEN with new gcc Err, is this a gcc 3.4 error? The new gcc version has not yet been imported into CVS; the logs you see on pointyhat are previews of what will happen when it is, so maintainers can start working on fixing the problems. See the emails I sent to ports@ recently about this. Kris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/LLlWry0BWjoQKURAgaoAJ42p5IVloTVyoisi3vDH+oSOVnlogCfSV8W LXGGMBodUMV4HVV2XrF/Ygk= =zU08 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--