Date: Tue, 28 Mar 2006 11:08:41 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: RJ45 <rj45@slacknet.com>, freebsd-questions@freebsd.org Subject: Re: problem building xorg Message-ID: <2196A0B4ECA7D60328719974@utd59514.utdallas.edu> In-Reply-To: <Pine.LNX.4.61.0603280728330.30682@slacknet.com> References: <Pine.LNX.4.61.0603280221040.19692@slacknet.com> <b2807d040603280559i393a5432tc6f868366064b561@mail.gmail.com> <Pine.LNX.4.61.0603280728330.30682@slacknet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========7D00D8C5405C85332DF7========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, March 28, 2006 07:35:41 -0700 RJ45 <rj45@slacknet.com> wrote: > > =3D=3D=3D> Script "configure" failed unexpectedly. > Please run the gnomelogalyzer, available from > "http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the > problem and suggest a solution. If - and only if - the gnomelogalyzer > cannot > solve the problem, report the build failure to the FreeBSD GNOME team at > gnome@FreeBSD.org, and attach (a) > "/usr/ports/x11-fonts/libXft/work/libXft-2.1.7/config.log", (b) the = output > of the failed make command, and (c) the gnomelogalyzer output. Also, it > might > be a good idea to provide an overview of all packages installed on your > system > (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, > copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) > with > the attachment. Try to avoid sending any attachments to the mailing list > (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists = are > usually discarded by the mailing list software. > *** Error code 1 > > Stop in /usr/ports/x11-fonts/libXft. > *** Error code 1 > > Stop in /usr/ports/x11/xorg-clients. > *** Error code 1 > > Stop in /usr/ports/x11/xorg. > rt-ca# > Did you download and run gnomelogalyzer? In general, when ports don't build, you should 1) run cvsup to ensure your=20 ports are up to date and 2) go to the port that's failing and make=20 deinstall clean and make install clean. 99% of the time, this will solve=20 your problem. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========7D00D8C5405C85332DF7==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2196A0B4ECA7D60328719974>