From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 18:12:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B49A16A417 for ; Thu, 11 Oct 2007 18:12:36 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 1480F13C45B for ; Thu, 11 Oct 2007 18:12:36 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.14.1) with ESMTP id l9BI8Ff9024405 for ; Thu, 11 Oct 2007 11:08:15 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.14.1/Submit) id l9BI8Fpv024404 for freebsd-current@freebsd.org; Thu, 11 Oct 2007 11:08:15 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Oct 2007 11:08:15 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20071011180815.GA23643@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Removing a symbol from Symbol.map? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 18:12:36 -0000 In my journey through the libm source code, I've discovered that msun/src/w_cabs.c contains a function named z_abs. This symbol appears in libm's Symbol.map, but z_abs has not prototype in any header file under /usr/include. Thus, it is namespace pollution that I'd like to remove. Do I simply remove z_abs from Symbol.map or is there more to it then this? PS: Yes, I know bde will probably object to removal of z_abs because of compatibility issues with fdlibm and the other *BSD. -- Steve