public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: getaddrinfo(): Bad value for ai_flags
Date: Thu, 28 Dec 2006 14:57:56 +0000 (UTC)	[thread overview]
Message-ID: <en0m1k$ik1$2@sea.gmane.org> (raw)
In-Reply-To: 4593A5E0.7010505@ilievnet.com

Daniel Iliev <danny@ilievnet.com> posted 4593A5E0.7010505@ilievnet.com,
excerpted below, on  Thu, 28 Dec 2006 13:09:20 +0200:

> whois (from net-misc/whois-4.7.19) gives me:
> 
> whois gentoo.org
> getaddrinfo(whois.publicinterestregistry.net): Bad value for ai_flags

[snip]

> So I did "emerge -1 glibc emul-linux-x86-baselibs libidn whois" but it
> didn't solve the problem. Any ideas?

I'm not a whois expert by far (anyone have a link to a decent tutorial
handy?), but on I'm on ~amd64 here, so have whois-4.7.20 (which is
keyworded ~amd64) merged, and that whois query returned what looked like
valid data to me, here.

One thing I can say, however, is that the emul-linux-x86-baselibs has
nothing to do with it, since it's 32-bit and wouldn't even load in the
process space of a 64-bit whois process.  32-bit and 64-bit processes and
libraries simply don't mix, the whole reason the 32-bit emul-linux-x86-*
and -bin packages are necessary in the first place.  (A very few packages,
including gcc/glibc/sandbox, compile separate code and normally separate
files for each bitness, but they are special cases.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2006-12-28 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 11:09 [gentoo-amd64] getaddrinfo(): Bad value for ai_flags Daniel Iliev
2006-12-28 14:57 ` Duncan [this message]

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='en0m1k$ik1$2@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox