From owner-freebsd-questions@FreeBSD.ORG Wed Sep 5 16:04:43 2012 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 0A5F01065675 for ; Wed, 5 Sep 2012 16:04:43 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from asbnvacz-mailrelay01.megapath.net (asbnvacz-mailrelay01.megapath.net [207.145.128.243]) by mx1.freebsd.org (Postfix) with ESMTP id BA38F8FC17 for ; Wed, 5 Sep 2012 16:04:42 +0000 (UTC) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.42]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id A6BEFA719D9 for ; Wed, 5 Sep 2012 12:04:41 -0400 (EDT) Received: (qmail 30816 invoked from network); 5 Sep 2012 16:04:41 -0000 Received: by simscan 1.4.0 ppid: 6145, pid: 24036, t: 0.2121s scanners: clamav: 0.88.2/m:52/d:10739 Received: from unknown (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Sep 2012 16:04:40 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 6597733C24; Wed, 5 Sep 2012 12:04:40 -0400 (EDT) From: Lowell Gilbert To: Mario Lobo References: <44txvds23l.fsf@lowell-desk.lan> <20120904230305.46a318b6@papi> Date: Wed, 05 Sep 2012 12:04:40 -0400 In-Reply-To: (Mario Lobo's message of "Wed, 5 Sep 2012 08:25:57 -0300") Message-ID: <44r4qg4fs7.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD-Questions@freebsd.org Subject: Re: Firefox install problem 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: Wed, 05 Sep 2012 16:04:43 -0000 Mario Lobo writes: > 2012/9/4 Warren Block > >> On Tue, 4 Sep 2012, Waitman Gobble wrote: >> >> On Sep 4, 2012 7:03 PM, "Mario Lobo" wrote: >>> >>>> >>>> All I've done was "csup -L 2 ports-supfile" with ports-www in it. >>>> Then cd /usr/ports/www/firefox; make with default options. >>>> >>>> As for my /etc/make.conf >>>> >>>> CPUTYPE?=nocona >>>> OVERRIDE_LINUX_BASE_PORT=f10 >>>> OVERRIDE_LINUX_NONBASE_PORTS=f10 >>>> WITH_KDE4=yes >>>> WITH_CUPS=yes >>>> WITH_ICONS=KDE4 >>>> WITHOUT_GNOME=yes >>>> PYTHON_DEFAULT_VERSION=python2.7 >>>> PERL_VERSION=5.10.4 >>>> >>>> If it is its fault, it will be the first time in around 3,5 years. >>>> >>> >>> did you _only_ csup www in ports? ill have to check but im not sure >>> libvpx >>> is in www... im not in a place to check at this exact second but my memory >>> is that is providing webm support so probably in audio or multimedia >>> >> >> multimedia/libvpx would not have been updated. Selectively updating ports >> is not supported. Symlinking libraries to missing versions is often a >> source of mysterious problems later. >> > > > I had run csup with ports-multimedia since the first libvpx error came up!. > Libvpx was already up to date by the way, and correctly installed. So i did > not Symlink a library to any "missing version". But not necessarily the version that your other ports had been tested against. This can lead to mysterious problems, as you may have noticed. > "Selectively updating ports is not supported". Then I must wonder why do > we have the option to put "ports-{$port}" inside the supfile, and not a > mandatory ports-all. Sometimes, for some purposes, it works, and keeping it around helps some experts (especially porters). But "not supported" means "please don't ask us to help you use it." That is, you should update the whole port tree and update all dependent ports before reporting a problem. Here is what you should do: (1) Update your ports tree. You can use any method to do this (e.g. cvs, cvsup, subversion, portsnap), but update the whole tree at the same time. (2) If step (1) did not update your INDEX file, update it now. Possible methods include "make fetch" and "make index". I you use portupgrade, "portsdb -Uu" is the best way. (3) cd /usr/ports && make clean Kind of overkill in most cases, but when your port tree is building in bogus directories for no apparent reason, overkill may save your butt. (4) Upgrade all of the ports that firefox depends on (and the ones they depend on). Tools like portmaster or portupgrade make this much easier. (5) Rebuild the vpx port, even if it's already up to date. (6) Then rebuild the firefox port.