From owner-freebsd-ports@FreeBSD.ORG Wed Jul 5 03:41:25 2006 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A86416A4E5 for ; Wed, 5 Jul 2006 03:41:25 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from ns1.scsiguy.com (www.scsiguy.com [70.89.174.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF73843D46 for ; Wed, 5 Jul 2006 03:41:24 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from mail.scsiguy.com (gibbs@aslan.scsiguy.com [70.89.174.89]) (authenticated bits=0) by ns1.scsiguy.com (8.13.6/8.13.6) with ESMTP id k653fNNA005349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 4 Jul 2006 21:41:23 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Tue, 04 Jul 2006 21:41:23 -0600 From: "Justin T. Gibbs" To: ports@FreeBSD.org Message-ID: <59892F1BBCF4052B1E3EFAFF@aslan.scsiguy.com> X-Mailer: Mulberry/4.0.0b4 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Fixing VNC port(s) for AMD64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 03:41:25 -0000 So I'm new to AMD64 and was surprised by the lack of VNC support for this platform. Its been a while since I've hacked ports (like more years than I have fingers on one hand), but I figured it couldn't be that hard to fix up one of the VNC ports and submit my work back. Boy was I wrong. I did get something to build and work, but my solution is not port worthy. Given my inexperience with the current ports system and the X11 build, is there anyone here I can team up with to develop a proper solution? Here's what I ended up doing to the vnc port: o Disable XFree86 4.3 fetches and replace with Xorg 6.9.0. o Apply all FreeBSD server and library patches for Xorg. o Correct vnc's supplied patch file to be compatible with the Xorg distribution (some hunks have already been applied). o Add -fPIC to the build of vnc components linked as libraries (required for AMD64 support). o Modify cf files to disable server extensions that require xf86 config and hw support inappropriate for a virtual Xserver like Xvnc. o Manually build libdamage which was referenced by the link of Xvnc, but not built for some reason. Since there are several ports that require a "ports system patched" version of an Xorg or XFree86 source tree, can we come up with a better solution than to extract the source and either include or reference all the patches to be applied in each port? I disabled extensions until all undefined references were removed from the link of Xvnc. While the resulting binary works as best I can tell, it may not be optimal. Someone with more Xserver experience would be a big help here. Anyway, I think that vnc is a critical piece of infrastructure for many types of server installations. I'd hate to see others burn a good half day or more trying to get vnc to work on their server. What can I do to further the cause of getting the port fixed? Thanks, Justin