Git development
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 1/6] Disable IPv6 support for Haiku
Date: Mon, 18 Aug 2008 22:04:29 +0200	[thread overview]
Message-ID: <20080818200429.GD3262@steel.home> (raw)
In-Reply-To: <795912D9-BAA1-4E42-A533-435CB1BCCCAC@web.de>

Andreas Färber, Mon, Aug 18, 2008 19:23:35 +0200:
> Am 17.08.2008 um 22:33 schrieb Alex Riesen:
>> Andreas Färber, Sun, Aug 17, 2008 10:56:56 +0200:
>>> +ifeq ($(uname_S),Haiku)
>>> +	NO_IPV6 = YesPlease
>>> +endif
>>
>> Does Haiku have no IPv6 support at all, or it is just the getaddrinfo
>> and the like functions which are missing?
>
> Haiku does not yet have complete IPv6 support afaik (would've been a  
> GSoC project), it does have getaddrinfo though. Not setting NO_IPV6  
> currently leads to compilation errors (redefinition of struct  
> sockaddr_in), I assume that should be fixed on their side of things.

Ah, that's what it was...

> In the current series of patches I had not included a check for  
> libnetwork in configure.ac, so that getaddrinfo does not get detected.  
> Would you prefer to have it already detected, but to override it via the 
> above Makefile line? (That works as well.) Or to have it detected but 
> have the user manually pass NO_IPV6=YesPlease to avoid a future revert of 
> that line?

I think your patch as-is will be preferred (it just works).
It is not a big deal to change it later.

      reply	other threads:[~2008-08-18 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17  8:56 [PATCH 1/6] Disable IPv6 support for Haiku Andreas Färber
2008-08-17 20:33 ` Alex Riesen
2008-08-18 17:23   ` Andreas Färber
2008-08-18 20:04     ` Alex Riesen [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=20080818200429.GD3262@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=andreas.faerber@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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