From owner-freebsd-ports@FreeBSD.ORG Sat Jun 13 21:40:15 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C578106564A for ; Sat, 13 Jun 2009 21:40:15 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 326E58FC1C for ; Sat, 13 Jun 2009 21:40:14 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: (qmail 9335 invoked by uid 89); 13 Jun 2009 20:01:40 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 13 Jun 2009 20:01:40 -0000 Message-Id: From: Dan Allen To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 13 Jun 2009 15:13:29 -0600 X-Mailer: Apple Mail (2.935.3) Subject: Re: Stop in /usr/ports/lang/gcc43 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 21:40:15 -0000 I am trying to upgrade Ruby, and build Firefox 3.0.11, and they both want to build gcc43 because of gfortran. Really? Firefox needs gfortran to build? I bet not. Anyway, when they try and build gcc43 (of May 31st) on my system, I get into an infinite loop by the pkg system saying that gcc43 requires gfortran to build, that gfortran is not present... the script finally dies. This happens even if I simply do this: cd /usr/ports/lang/gcc43 make It dies there too. So now I cannot upgrade firefox, noway, nohow. Interestingly enough I have gcc44 (with gfortran44!) on the system but these dependencies do not consider that a substitute. I have cvsup'd the ports trees, done portsdb -uF, pkgdb -F, and portupgrade -ar a billion times. It does not help. Everything was fine yesterday, Jun 12th for me. The change came in with Firefox 3.0.11 and some /usr/ports/devel/nspr package that Firefox needs. Something is messed up in the dependencies. Dan Allen