From owner-freebsd-ports@freebsd.org Sat Jan 20 22:26:39 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30644ECA312 for ; Sat, 20 Jan 2018 22:26:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E7FEE6DDE7 for ; Sat, 20 Jan 2018 22:26:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0KMQdiK082887 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 20 Jan 2018 14:26:40 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0KMQd7h082886 for freebsd-ports@freebsd.org; Sat, 20 Jan 2018 14:26:39 -0800 (PST) (envelope-from fbsd) Date: Sat, 20 Jan 2018 14:26:38 -0800 From: bob prohaska To: freebsd-ports@freebsd.org Subject: Use of undeclared identifier 'fpgetmask' Message-ID: <20180120222638.GA82875@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2018 22:26:39 -0000 use of undeclared identifier 'fpgetmask' A web search for the phrase finds a very few references, most prominently from the year 2014: https://www.where-i-go.com/tag/fpsetmask but the context is different (mysql server). There is a workaround detailed in the web page, but after nearly four years it's hard to believe that's still appropriate. Is there a more up-to-date solution? Thanks for reading, bob prohaska