From owner-freebsd-x11@FreeBSD.ORG Thu Oct 24 22:13:05 2013 Return-Path: Delivered-To: freebsd-x11@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 ESMTP id 44627925; Thu, 24 Oct 2013 22:13:05 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep25.mx.upcmail.net (fep25.mx.upcmail.net [62.179.121.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5CA242EDF; Thu, 24 Oct 2013 22:13:04 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep19-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131024212557.UFO10006.viefep19-int.chello.at@edge03.upcmail.net>; Thu, 24 Oct 2013 23:25:57 +0200 Received: from [127.0.0.1] ([178.84.134.112]) by edge03.upcmail.net with edge id h9Rw1m00N2Rg3Ey039RwHh; Thu, 24 Oct 2013 23:25:57 +0200 X-SourceIP: 178.84.134.112 Message-ID: <5269900A.1050509@rainbow-runner.nl> Date: Thu, 24 Oct 2013 23:24:26 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: sbruno@freebsd.org, freebsd-X11 Subject: Re: xorg-xserver build failures? References: <1382645282.1541.5.camel@localhost> In-Reply-To: <1382645282.1541.5.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 131024-0, 24-10-2013), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 22:13:05 -0000 On 24-10-2013 22:08, Sean Bruno wrote: > =========================================================================== > ======================= extract-depends>============================ > =========================================================================== > =======================> ============================ > By default, the X Server installs as a set-user-id root binary. When run > by > a normal user, it checks arguments and environment as done in the > x11/wrapper > port before handling them normally. If you are concerned about the > security > of this, but still want to run an X Server (for example using > xdm/kdm/gdm, > which will still run the server as root), you can cancel the build and > set > xorg-server_UNSET=SUID in /etc/make.conf. > ===> Fetching all distfiles required by xorg-server-1.7.7_11,1 for > building > ===> Extracting for xorg-server-1.7.7_11,1 > => SHA256 Checksum OK for xorg/xserver/xorg-server-1.7.7.tar.bz2. > =========================================================================== > =======================> ============================ > =========================================================================== > =======================> ============================ > ===> Patching for xorg-server-1.7.7_11,1 > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-Xext-xace.c > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-Xserver-os-xprintf.c > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-include_eventstr.h > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-os-utils.c > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-dix_events.c > ===> Applying extra > patch /usr/ports/x11-servers/xorg-server/files/extra-Xserver-hw-xfree86-common-xf86Config.c > ===> Applying extra patch /extra-old-dix_dixfonts.c > cat: /extra-old-dix_dixfonts.c: No such file or directory > I can't seem to find a patch in there anywhere. > *** Error code 2 > > Stop. > make: stopped in /usr/ports/x11-servers/xorg-server > ===> Cleaning for xorg-server-1.7.7_11,1 > build of /usr/ports/x11-servers/xorg-server ended at Thu Oct 24 16:06:01 > EDT 2013 > I made a typo in the Makefile that caused that, if you update your ports tree it will be fixed. Sorry about that. -Koop