From owner-freebsd-ports Wed Apr 3 6:55: 8 2002 Delivered-To: freebsd-ports@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id D4BF037B416 for ; Wed, 3 Apr 2002 06:54:58 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id F2B509B15; Wed, 3 Apr 2002 09:54:42 -0500 (EST) Date: Wed, 3 Apr 2002 09:54:42 -0500 From: Will Andrews To: "Hartmann, O." Cc: Will Andrews , freebsd-ports@freebsd.org Subject: Re: XFree86-4.2 more installation problems! Message-ID: <20020403145442.GD75343@squall.waterspout.com> Mail-Followup-To: "Hartmann, O." , Will Andrews , freebsd-ports@freebsd.org References: <20020403120815.GB75343@squall.waterspout.com> <20020403150301.L47621-100000@klima.physik.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020403150301.L47621-100000@klima.physik.uni-mainz.de> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Apr 03, 2002 at 03:11:22PM +0200, Hartmann, O. wrote: > You are right, but 'fiddling' means sometimes doing a traditional job like > installing the software by hand. > > In my case, Xft seems to lack in some header files I can not install > or I do not know where to find. freetype in its newest version IS definitely > broken when using the ports collection, it is the install routine which makes > things impossible. It uses 'make' instead of 'gmake' as mentioned. After the > installation by hand I can also not install XFree86, because it lacks in a > header file named ft2xxxx.h or similar. > > The XFree86 port depends on freetype - so IT IS a XFree86 problem due to the fact > of dependencies. On one machine I did the task - but it worked because an > older freetype2 port has been installed already and I did not delete the X11R6 > directory. > > Installations of XFree86 on a freshly installed system also fails. > > I do not know what must happen in addition to say: this port is broken! > All the discussions about the new meta-port philosophy is obsolete due > to the fact that it is not working as exspected. > > Well, we are not talking about development or using XFree86 'at home' or for > toys. I'm sorry using those harsh words, but at the moment 'tempus fugit', > time runs away and we have a lot of work to do. Installing XFree86 by hand is > no alternative because next time I run into trouble with other ports which need > to know how XFree86 has been installed by the ports system ... I'm sorry, but I can't help people when I don't get enough details on the problem. You haven't shown any logs or any other kind of information about your system (that hasn't already been distilled by you -- this information is worthless). The XFree86 ports work fine for a large number of people including myself, although I have heard many reports of people improperly upgrading or installing it. I have no good solution for those situations yet. If you choose to bypass the ports tree that's your problem. BTW, if you are going to do things on production machines that have no forgiveness for mistakes, stick to the releases. Regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message