From owner-freebsd-questions Mon Mar 1 17:21: 4 1999 Delivered-To: freebsd-questions@freebsd.org Received: from merki.connect.com.au (merki.connect.com.au [192.189.54.36]) by hub.freebsd.org (Postfix) with ESMTP id C5BB014C56 for ; Mon, 1 Mar 1999 17:21:00 -0800 (PST) (envelope-from david.gray@computer.org) Received: from shrike.UUCP (uucp@localhost) by merki.connect.com.au with UUCP id MAA08029 (8.8.8/IDA-1.7 for freebsd-questions@freebsd.org); Tue, 2 Mar 1999 12:20:42 +1100 (EST) Received: from computer.org (cobra [20.10.51.54]) by shrike.syd.csa.com.au (8.8.7/8.8.7) with ESMTP id MAA02823 for ; Tue, 2 Mar 1999 12:01:00 +1100 (EST) Message-ID: <36DB384C.EE6891E5@computer.org> Date: Tue, 02 Mar 1999 12:01:00 +1100 From: David Gray X-Mailer: Mozilla 4.05 [en] (X11; I; IRIX 6.3 IP32) MIME-Version: 1.0 To: freebsd-questions Subject: XFree86-3.3.3.1 port breaks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I posted this to freebsd-stable a week or so ago, but I haven't got any replies. Perhaps people didn't realise it was a question :) Basically, I can't build XFree86. The makefile breaks when it tries to apply the patches to the source distribution. The output from make is appended to this mail. I run 3.1-stable, about 2 weeks old, and have an up-to-date ports tree. Any help would be greatly appreciated. Thanks, David. ---- /usr/ports/x11/XFree86 # make ===> Extracting for XFree86-3.3.3.1 >> Checksum OK for xc/X333src-1.tgz. >> Checksum OK for xc/X333src-2.tgz. >> Checksum OK for xc/3.3.3-3.3.3.1.diff.gz. ===> Patching for XFree86-3.3.3.1 ===> Applying distribution patches for XFree86-3.3.3.1 ===> Applying FreeBSD patches for XFree86-3.3.3.1 2 out of 4 hunks failed--saving rejects to programs/xdm/session.c.rej *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message