From owner-freebsd-ports Sun Nov 8 08:10:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23398 for freebsd-ports-outgoing; Sun, 8 Nov 1998 08:10:26 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23376; Sun, 8 Nov 1998 08:10:22 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from client201-122-14.bellatlantic.net (client201-122-14.bellatlantic.net [151.201.122.14]) by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id LAA26093; Sun, 8 Nov 1998 11:06:36 -0500 (EST) Newsgroups: comp.unix.bsd.freebsd.misc Date: Sun, 8 Nov 1998 11:05:27 +0000 (GMT) From: Donn Miller X-Sender: dmm125@localhost To: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Ports/patches for X332servonly Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just trying to find out if anyone did a port and/or patch for X332servonly.tgz. It's like the full source for XFree86 but it doesn't include the stuff for building shared libs. I need the source code so I can modify it to make a driver for my chipset, which is unsupported. BTW, building XFree86 from sratch is pretty nasty. One minor change to any of the config files in xc/config/cf sometimes throws the whole build out of whack. The shared/static libs build OK, but when it comes time to link all the object files and libs together to produce the X-server, massive amounts of errors about "undefined reference to ..." come pouring out like crazy. This is in the subdir xc/programs/Xserver/hw... I tried building it w/out changing any source at first, just to see if it would compile, and it won't compile. So anyone successfully built the XFree86 servers from source on 3.0-R? Thanks for any help you can provide, Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message