From owner-cvs-src@FreeBSD.ORG Sun Jan 9 09:28:18 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A06E16A4CE; Sun, 9 Jan 2005 09:28:18 +0000 (GMT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2320C43D49; Sun, 9 Jan 2005 09:28:18 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com (ip68-230-188-82.dc.dc.cox.net [68.230.188.82]) (authenticated bits=0) by pittgoth.com (8.12.10/8.12.10) with ESMTP id j099SGoa032225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Jan 2005 04:28:17 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Sun, 9 Jan 2005 04:28:16 -0500 From: Tom Rhodes To: Colin Percival Message-ID: <20050109042816.7e1c9ef1@mobile.pittgoth.com> In-Reply-To: <41E0F853.6060207@wadham.ox.ac.uk> References: <200501082256.j08Mu9XJ015280@repoman.freebsd.org> <41E0D155.9020704@wadham.ox.ac.uk> <20050109040059.6e14a902@mobile.pittgoth.com> <41E0F853.6060207@wadham.ox.ac.uk> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/ping6 Makefile ping6.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 09:28:18 -0000 On Sun, 09 Jan 2005 01:24:35 -0800 Colin Percival wrote: > Tom Rhodes wrote: > > Colin Percival wrote: > >>Judging by the latest tinderbox build, it looks like you > >>need to replace "size_t" with "socklen_t" at line 1772 of > >>ping6.c before setting WARNS=6. > > > > But I only bumped it to two. > > Err, yeah. That's what I meant. :-) > > I was getting confused with a different WARNS bump. Tis ok, should be fixed now. You were right, I missed this because I didn't perform a 64-bit test. Pass the pointy hat for me to bear for my mistake. :) -- Tom Rhodes