From owner-freebsd-ports@FreeBSD.ORG Thu Jul 17 20:15:43 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99D0D37B40F; Thu, 17 Jul 2003 20:15:43 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF99F43FCB; Thu, 17 Jul 2003 20:15:32 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 03D1066EA9; Thu, 17 Jul 2003 20:15:25 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id A3AB7C16; Thu, 17 Jul 2003 13:59:46 -0700 (PDT) Date: Thu, 17 Jul 2003 13:59:46 -0700 From: Kris Kennaway To: Motoyuki Konno Message-ID: <20030717205946.GA34884@rot13.obsecurity.org> References: <20030713010957.2181af46.yosimoto@waishi.jp> <20030717092556.70a96dc9.yosimoto@waishi.jp> <200307171511.h6HFBdPa000471@mail.mk.bsdclub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <200307171511.h6HFBdPa000471@mail.mk.bsdclub.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: some ports are broken after upgrading GCC 3.3.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 03:15:44 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 18, 2003 at 12:11:39AM +0900, Motoyuki Konno wrote: > Add Cc: to -current list. >=20 >=20 > This seems to be "varargs.h" problem. It seems that all C source > which use varargs.h and va_dcl become error on GCC 3.3.1 system. This is a known problem. Can you develop a fix? Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/Fw5CWry0BWjoQKURAjUtAKDgJuxttivNHwi9t+aOKWs83NFmmgCeJE3P Lv50gMHHpEmk12Cc76EfuP4= =gwSc -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--