From owner-freebsd-emulation@FreeBSD.ORG Tue Sep 16 08:36:11 2014 Return-Path: Delivered-To: vbox@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FFD7B3D for ; Tue, 16 Sep 2014 08:36:11 +0000 (UTC) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D78A692D for ; Tue, 16 Sep 2014 08:36:10 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id g201so3358010oib.22 for ; Tue, 16 Sep 2014 01:36:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=pczKexI4f7WpwBTMwCZjxHApm322XXZaOv1ZZz41JlU=; b=CyjnLB7cPYQ8HcUdzgfplTPQV//fvjWxOM7xSC9Q7qi9Apb8U6Kw3zipnL5PmwBdWV acd6ri1AZoHzeDaTVfAEsHu8VSEyizumpBzG8PTSFTIHQ0kzypKDu8WH7+ByGd7DvJ4g ZkCrlxyAoqbktRpBxUdGHXQO+dH7BUh9lWxOk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pczKexI4f7WpwBTMwCZjxHApm322XXZaOv1ZZz41JlU=; b=jKI+IBeCfDyINGpHGNQJCLtPbPKU6UiuHDk+M2Nk0FPnCHeVSkXwCTnynsf7dCsaq0 aU4Gl7yujnIiZtDNX6D70xzHen0y7tuNSQbI8x31ORIDDgU6+VIuF2rot4zsOv2PepYb +WXvIPpsj1sddbjahqk4cpBGiE9ZQ4xhkDyJ1J1c9aoWiMbGWhLjWPg3RaoWg9JQrktE YYXt2xrhCYotRRzDst/s65fqrmI7dN3y5u6wWSHRqVLJZxRnqjVBTr9pdNOr/3SM5pC6 wSlFB2Rqr8aCS2Mk451wWeY8BBWf5sN3mzR9SkUyjVvp68vDnIRZW1EaSo4EwYX3Xe2B ozPA== X-Gm-Message-State: ALoCoQngJWzKK4p4utYUvUlI43AwWt1GNclcuzHCLKrjC1e5XRaQYalxi0KUe7DvkvNMTZIAzvFr MIME-Version: 1.0 X-Received: by 10.182.79.65 with SMTP id h1mr14932583obx.53.1410856570101; Tue, 16 Sep 2014 01:36:10 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.76.141.136 with HTTP; Tue, 16 Sep 2014 01:36:10 -0700 (PDT) X-Originating-IP: [2001:470:701f:7000::10] In-Reply-To: References: Date: Tue, 16 Sep 2014 10:36:10 +0200 X-Google-Sender-Auth: FXUVSn2VJH6W_q12is33LdXpxv0 Message-ID: Subject: Re: Cannot set VBOX_USE_IPV6 for VNC Server (VBoxVNC.cpp) From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= To: Gresnald Orlas Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 16 Sep 2014 11:14:01 +0000 Cc: vbox@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 08:36:11 -0000 On Tue, Sep 16, 2014 at 3:16 AM, Gresnald Orlas wrote: > Hi, > > I recently had a problem where the VNC server in VirtualBox would not bind > to any IPV6 port except for the default. I did some research and found > this < > http://lists.freebsd.org/pipermail/freebsd-emulation/2014-January/011194.html> > and this < > http://newsarc.net/showthread.php/muc.lists.freebsd.emulation/Ports174976%3A%20Fix%20For%20IPv6%20Port%20Setting/4E0B86FF-9C4D-4CDA-87FC-D6F75926695F@lassitu.de> > After finding the last part I verified that the newer code is unpacked in > the ports directory. After trying several things I could not get the > VBOX_USE_IPV6 bit to be set and the program always compiled with the > default (broken) code. Anyway after playing around some more it looks to > me like kmk ignores /etc/make.conf and any CFLAGS passed in via the port > 'make CFLAGS=' command. I could be doing something obviously wrong, but I > think I am testing this right. Perhaps kmk is supposed to work this way? > In any case I thought you might want to know. I checked the IRC channel, > but no maintainers were around so I am sending this to vbox@freebsd.org > (maintainer) instead. Hope this helps someone. In the meantime for myself > I have a patch which takes away the code for the default behavior from > VBoxVNC.cpp directly. If am doing something obviously wrong please let me > know so I can do upgrades correctly and drop my ugly patch. No kBuild (kmk) is not supposed to work that way. You need to patch the cpp file as you did if you want/need that. We did include that change in the port some time ago but it caused some serious regression for other users so we had to revert it. That code is definitely a mess in vbox and just enabling that define is only the simple part of the work. -- Bernhard Froehlich http://www.bluelife.at/