From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: YAMAMOTO Mitsuharu Newsgroups: gmane.emacs.devel Subject: Re: trunk build failure on Solaris 2.6 Date: Sun, 21 Oct 2007 14:10:24 +0900 Organization: Faculty of Science, Chiba University Message-ID: References: <871wbr4x1v.fsf@stupidchicken.com> <87y7dz4tsx.fsf@stupidchicken.com> <87myuenavw.fsf@stupidchicken.com> <200710192032.l9JKW1MI003082@oogie-boogie.ics.uci.edu> <87y7dyvnt2.fsf@stupidchicken.com> <87ejfp7m33.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1192943445 6818 80.91.229.12 (21 Oct 2007 05:10:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 21 Oct 2007 05:10:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 21 07:10:46 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IjT5I-0007nv-B1 for ged-emacs-devel@m.gmane.org; Sun, 21 Oct 2007 07:10:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IjT5A-0003XT-5y for ged-emacs-devel@m.gmane.org; Sun, 21 Oct 2007 01:10:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IjT57-0003Uc-3T for emacs-devel@gnu.org; Sun, 21 Oct 2007 01:10:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IjT55-0003Qm-AJ for emacs-devel@gnu.org; Sun, 21 Oct 2007 01:10:32 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IjT55-0003QR-65 for emacs-devel@gnu.org; Sun, 21 Oct 2007 01:10:31 -0400 Original-Received: from ntp.math.s.chiba-u.ac.jp ([133.82.132.2] helo=mathmail.math.s.chiba-u.ac.jp) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IjT53-0000fj-Nu for emacs-devel@gnu.org; Sun, 21 Oct 2007 01:10:30 -0400 Original-Received: from church.math.s.chiba-u.ac.jp (church [133.82.132.36]) by mathmail.math.s.chiba-u.ac.jp (Postfix) with ESMTP id B341C2C43; Sun, 21 Oct 2007 14:10:24 +0900 (JST) In-Reply-To: <87ejfp7m33.fsf@stupidchicken.com> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/23.0.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) X-detected-kernel: by monty-python.gnu.org: NetBSD 3.0 (DF) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:81335 Archived-At: >>>>> On Sat, 20 Oct 2007 13:05:52 -0400, Chong Yidong said: > YAMAMOTO Mitsuharu writes: >>>>>>> On Fri, 19 Oct 2007 16:42:33 -0400, Chong Yidong >>>>>>> said: >> >>> Could a Mac maintainer try to find out why it's not working on >>> that platform? >> >> As address queries via getaddrinfo are normally forwarded to a >> daemon called lookupd on Mac OS X, I suspect it doesn't make sense >> to call res_init before getaddrinfo on that platform in the first >> place. > Then this bit of code in the configure script should fail, but it > apparently succeeds; that's why HAVE_LIBRESOLV is defined. I was not talking about how the configure script works, but whether the `res_init' call makes sense on Mac OS X in the first place. The intention of the `res_init' call before getaddrinfo is, as mentioned in configure.in, to detect /etc/resolv.conf changes by initializing some internal states of the resolver routine executed in the Emacs process. But on Mac OS X, and possibly also on some other platforms, the actual resolution is performed by an external process, and thus the Emacs process is not responsible to detect the /etc/resolv.conf changes. On such platforms, the `res_init' call does not make sense whether or not the configure script detects the existence of that symbol. YAMAMOTO Mitsuharu mituharu@math.s.chiba-u.ac.jp