all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: trunk build failure on Solaris 2.6
Date: Sun, 21 Oct 2007 14:10:24 +0900	[thread overview]
Message-ID: <wlk5phm4sf.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <87ejfp7m33.fsf@stupidchicken.com>

>>>>> On Sat, 20 Oct 2007 13:05:52 -0400, Chong Yidong <cyd@stupidchicken.com> said:

> YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:
>>>>>>> On Fri, 19 Oct 2007 16:42:33 -0400, Chong Yidong
>>>>>>> <cyd@stupidchicken.com> 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

  reply	other threads:[~2007-10-21  5:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  0:45 trunk build failure on Solaris 2.6 Katsumi Yamaoka
2007-10-19  2:50 ` William Xu
2007-10-19  3:12 ` Chong Yidong
2007-10-19  3:51   ` William Xu
2007-10-19  4:22     ` Chong Yidong
2007-10-19  5:47       ` William Xu
2007-10-19 15:29         ` Chong Yidong
2007-10-19 16:20           ` William Xu
2007-10-19 19:48       ` Chong Yidong
2007-10-19 20:31         ` Dan Nicolaescu
2007-10-19 20:42           ` Chong Yidong
2007-10-20  1:42             ` YAMAMOTO Mitsuharu
2007-10-20 17:05               ` Chong Yidong
2007-10-21  5:10                 ` YAMAMOTO Mitsuharu [this message]
2007-10-21  5:46                   ` William Xu
2007-10-22 14:46                   ` Chong Yidong
2007-11-05 11:12                     ` Mark Aufflick
2007-11-06  2:15                       ` Richard Stallman
2007-10-21  2:22             ` William Xu
2007-10-20  0:31           ` Evil Boris
2007-10-19  7:10     ` Cyrus Harmon
2007-10-19  4:33   ` Katsumi Yamaoka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wlk5phm4sf.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.