Date: Thu, 18 Jun 2009 23:03:48 -0600 From: Tim Judd <tajudd@gmail.com> To: Leslie Jensen <leslie@eskk.nu> Cc: freebsd-questions@freebsd.org Subject: Re: Now pkg-config trouble.................Re: startx does not work, startxfce4 does! Message-ID: <ade45ae90906182203h72040c63y5970075bdbdb54ff@mail.gmail.com> In-Reply-To: <4A3B1924.6040901@eskk.nu> References: <4A39197D.6000501@eskk.nu> <4ad871310906170953r56827e13wb4fac8473ac58dd5@mail.gmail.com> <4A3B1924.6040901@eskk.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
Leslie, The given port dirs (x11/xorg, etc) still probably have their work directory, which have the tokens/markers that particular stages of the port build have been done, such as the installation. rm -rf /usr/ports/*/*/work rehash cd /usr/ports/x11/xorg make install Please try that. First removes the work dir that contains the tokens, second updates root's available application hash, third and forth rebuild xorg Since xorg is so large, and receives very few (in relation to the total number of packages) updates, a quick-n-dirty way to get running is to add the package, and then update the outdated ones. pkg_add -r xorg portmaster -a I follow this same pattern on all BIG ports.. gnome2, kde3/4, xorg, and then let the portmaster update the old outdated ports that got installed. There is no functional difference between a package installed and a port installed with no options/config tweaked. Please try this. Write to us if you keep having problems
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90906182203h72040c63y5970075bdbdb54ff>