zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
	"Will Day" <willday@rom.oit.gatech.edu>,
	"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: test for network libraries (for test only)/problems with name resolution
Date: Fri, 8 Sep 2000 10:05:01 +0400	[thread overview]
Message-ID: <000001c0195a$b9945130$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000908041404.ZM31745@candle.brasslantern.com>


Yes, I was almost sure gethostbyname2 would be a problem. As I wrote before it
means, Solaris 7 headers or libraries are broken. O.K. it means, patch had not
fixed the bug anyway, so I was right to remove it.

>
>
> On Sep 7,  6:16pm, Will Day wrote:
> } Subject: Re: PATCH: test for network libraries (for test only)/problems wi
> }
> } I dunno. If I remove the "static" from the zftp.c declaration, it
> } should work fine, but I'm not sure what problems that might introduce.
>
> It'll just mean you can't look up names for IPv6 hosts, I think.
>

IPv6 is the keyword. We need the gethostbyname2/getipnodebyname, inet_pton etc
*only* if we want to do IPv6. Conversely, we cannot do IPv6 without these
functions (well, actually, RFC for gethostbyname2 - forgot the number -
states, that implementation of gethostbyname may return IPv6 addresses, but it
looks too obscure. And it is is obsolete by getipnodebyname anyway). That was
what I  was about to do - remove all local (re-)definitions of resolver
functions and make better guess about SUPORT_IPV6, i.e. do not use IPv6
functions unless we are doing IPv6 and do not do IPv6 unless we have all
prerequisites. That should also solve my problem (with incorrect use of
gethostbyname2). Unfortunately, I do not have any IPv6 implementation here to
test it. Is there some system that supports IPv6 without proper resolver
support?Zefram, you added IPv6 support IIRC?

Does Solaris 7 support IPv6?

-andrej


  reply	other threads:[~2000-09-08  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000821092904.A32199@lorien.emufarm.org>
2000-08-22 13:15 ` Andrej Borsenkow
2000-08-22 13:43   ` Roland Jesse
2000-08-22 17:02   ` Bart Schaefer
2000-08-23  6:55     ` Andrej Borsenkow
2000-09-04 13:39     ` Andrej Borsenkow
2000-09-06 15:52       ` Removed " Andrej Borsenkow
2000-09-07 22:16       ` Will Day
2000-09-08  4:14         ` Bart Schaefer
2000-09-08  6:05           ` Andrej Borsenkow [this message]
2000-09-08  6:39             ` Will Day
2000-09-08  7:28             ` OT: " Andrej Borsenkow
2000-09-08 20:31             ` Zefram

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='000001c0195a$b9945130$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=schaefer@candle.brasslantern.com \
    --cc=willday@rom.oit.gatech.edu \
    --cc=zsh-workers@sunsite.auc.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).