From owner-freebsd-questions@FreeBSD.ORG Fri Jun 19 05:03:48 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D1D1065680 for ; Fri, 19 Jun 2009 05:03:48 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9EDD28FC0C for ; Fri, 19 Jun 2009 05:03:48 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so807626qwe.7 for ; Thu, 18 Jun 2009 22:03:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Zuj5VjmNV+p/nJVqskOtFk5TzM/G81kTv9prAbB+oSk=; b=DCRQgKb/JKc89IJSHjuTa0/8CgSMxUU0rfxQ+HmXwnVGGvqen799WJodfG+KUERJx2 PGekcAaPxJYRT/svhU3smJuZPti1RQB12U1fL16ziQ5QyM2iKeLSFmuBsO8tuI4laOl0 Z8tM95L9QbIhzhZksmi09h6U+XpEewg63allk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uO1w+BWkZ0qSQIG6Pdgawa56SGvv2eU64lWvmmHQahQWVRDww3fO3Q5zIPDn/249bj Vvjx5rsRD05UZwZjAX+CrG1Az+23/mUMuCYEuBCiFHvzFZiknarWfyQYgOgYnxqCSe/3 2e/LITCDxxdw2s4w9hjrPzDaYc+4fM1nWaIqg= MIME-Version: 1.0 Received: by 10.220.71.10 with SMTP id f10mr2319717vcj.13.1245387828066; Thu, 18 Jun 2009 22:03:48 -0700 (PDT) In-Reply-To: <4A3B1924.6040901@eskk.nu> References: <4A39197D.6000501@eskk.nu> <4ad871310906170953r56827e13wb4fac8473ac58dd5@mail.gmail.com> <4A3B1924.6040901@eskk.nu> Date: Thu, 18 Jun 2009 23:03:48 -0600 Message-ID: From: Tim Judd To: Leslie Jensen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Now pkg-config trouble.................Re: startx does not work, startxfce4 does! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2009 05:03:49 -0000 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