From owner-cvs-src@FreeBSD.ORG Mon Aug 27 15:10:49 2007 Return-Path: Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8450816A418; Mon, 27 Aug 2007 15:10:49 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id C8D4113C459; Mon, 27 Aug 2007 15:10:48 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l7RFAYDJ070665; Mon, 27 Aug 2007 19:10:34 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l7RFAYu9070664; Mon, 27 Aug 2007 19:10:34 +0400 (MSD) (envelope-from yar) Date: Mon, 27 Aug 2007 19:10:34 +0400 From: Yar Tikhiy To: Alexander Leidinger Message-ID: <20070827151033.GM21352@comp.chem.msu.su> References: <20070824215515.GF16131@turion.vk2pj.dyndns.org> <20070824.172212.74696955.imp@bsdimp.com> <200708270850.20904.jhb@freebsd.org> <20070827135625.GF29854@garage.freebsd.pl> <20070827162655.3e3x0cse8w44o4o4@webmail.leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070827162655.3e3x0cse8w44o4o4@webmail.leidinger.net> User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Mon, 27 Aug 2007 15:46:15 +0000 Cc: src-committers@FreeBSD.org, Pawel Jakub Dawidek , John Baldwin , peterjeremy@optushome.com.au, alfred@FreeBSD.org, cvs-all@FreeBSD.org, deischen@FreeBSD.org, cvs-src@FreeBSD.org, Warner Losh Subject: Re: cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 27 Aug 2007 15:10:49 -0000 On Mon, Aug 27, 2007 at 04:26:55PM +0200, Alexander Leidinger wrote: > > So the really important thing for you is: How many ports are affected > by this change? > > Does anyone have an estimate for this? > > If not, does someone has an exhaustive list of affected symbols? I can > write a short script which has a look into each installed port to > determine if it is affected or not (based upon the assumption that you > don't mind if we overlook a few things... I'm not sure if statically > linked binaries contain enough information). With the resolution approaching to avoid compatibility in fts(3) now and my experiment on improving src/Makefile.inc1 going on really well, I think I should estimate which ports are going to be affected. I'll do so by searching binary packages for CURRENT, so some ports can slip through my sieve. The symbols to look for match the simple pattern: fts_* (or regexp: ^fts_.*). I don't think there are a lot of ports using those functions. Here's the exact list of symbols to be affected: fts_open fts_close fts_read fts_set fts_children fts_get_clientptr fts_get_stream fts_set_clientptr -- Yar